We need get pdfs and encript them in Appengine (GAE).
We have tried to do it with itext, pdfjet and pdfbox they doesn`t work in appengine.
Somebody knows a library which works well on GAE?, or could help us to identify the problems with the other libraries to work on GAE?
Best Regards
I'm using a special version of iText, prepared for GAE - https://github.com/bedatadriven/appengine-export
It's based on old version of iText (last version under LGPL licence). But it works well, I don't have any problem.
Related
We have a third party native SDK that is done in AndroidX, to which extent we can use it in codenameone, and what is the roadmap of AndroidX integration codenamone.
Many thanks for your prompt response, we have some decisions to make.
I moved the task for AndroidX support to the 7.0 timeframe. Initially we hoped to get 7.0 out the door much sooner but since it was delayed it makes sense to do that task now.
Some developers were able to get AndroidX libraries working with some creative build hints but I can't find their posts at the moment.
Thank you a lot Shai,
We also have been able to get it work but by modifying the config of the Android studio project.
Can you confirm, the other developpers did on the CN1 build hint ?
Thanks a lot
I've been trying to download the parse4j from Thiagolocatelli but they're missing version 1.5-SNAPSHOT which includes a third parameter for Parse.initialize(), but I can't download version 1.5-SNAPSHOT from github nor from Maven repository, people talk about version 1.5-SNAPSHOT but looking at the Maven repository: https://mvnrepository.com/artifact/com.github.thiagolocatelli/parse4j there is no version 1.5-SNAPSHOT. So is it possible to use parse4cn1 in non cn1 projects like Android Studio projects? Will library work?
It is possible to use parse4cn1 in a regular Java project as documented here. In fact, the parse4cn1 unit test application uses this approach successfully. As already mentioned by Shai, you'll have some dependencies on some CN1-specific functionality but that is available via the CN1 JavaSE port.
For Android, I'll recommend using the native Android Parse SDK directly. The API is slightly different from that of parse4cn1 but in most cases similar. Moreover, the SDK provides more functionality such as a local data store.
No.
The code uses ConnectionRequest and similar Codename One specific classes to implement parse support.
This morning, I tried to get a coop student up and running on an older version of the Google App Engine for Eclipse plugin.
The following website and all related links appear to have been wiped off the face of the earth:
https://developers.google.com/eclipse/
Is this just down at the moment?
Is it possible to get older versions of the plugin?
While it is correct that the Google Plugin for Eclipse has been removed from Google's documentation, it is still available.
To install it, in Eclipse Neon, click "Install new Software" and add in this URL.
http://dl.google.com/eclipse/plugin/4.6
Next, click through the dialogues to allow the installation, and restart Eclipse.
While Google has chosen to stop supporting this, I personally feel that the new Cloud Tools for Eclipse plugin is just not ready. Also, in the early days, JDO was what many people were using on top of the data layer, and since GAE has been around for 10+ years, many of us have a lot of infrastructure built on top of this that is costly to change. While it's still possible, in theory, to run the DataNucleus enhancer manually, it's a huge pain that requires in-depth knowledge of the inner workings of GAE and DataNucleus and knowledge of which dependencies go together. It may have been well-documented in the past, but today it is not.
But be warned, one of our engineers recently lost the ability to deploy the project to Google App Engine using the GPE and was forced to use the gcloud tool, which doesn't seem to have sensible defaults, like deploying to a non-default version and instead will deploy straight to default, well, by default. So we're writing a script around that command that will pass in --no-promote so it doesn't immediately start migrating traffic... Visit the gcloud reference for app deploy for more details. Good luck!
For more information on the install process, please see How to install Google Plugin for Eclipse on mkyong.com.
GPE is indeed gone. It was not up to date and many parts of it no longer functioned. Over the coming year, even more core functionality was going to break. We wouldn't be doing anyone any favors by letting them invest their time in a broken tool. This is doubly true for new users such as your students. There are some old GPE snapshots floating around here and there, but those don't really work with GCP in 2018.
That official documentation is most likely gone for good, the plugin was deprecated in favour of the Google Cloud Tools for Eclipse. From Migrating from the Google Plugin for Eclipse:
The Google Plugin for Eclipse is deprecated and will not be supported
beyond Eclipse 4.6 (Neon). It will be removed in early 2018.
This document describes how to migrate a project that uses the Google
Plugin for Eclipse to the supported tooling.
You can check the snapshots of the docs on the Wayback Machine, and maybe still find the matching code repositories, if they haven't been removed as well.
But it's probably a good idea to switch to the supported tools sooner than later, especially since they're just getting started.
Related: Migrating GAE project to Java 8 - get XML validation error after adding runtime property to appengine-web.xml
Does Google still support SL4A for Android.
I have created an apk file for SL4A which is A6 using the old source code, could anyone kindly let me know if the source code for SL4A is available for the latest Android version(A16>).
Google never actually supported SL4A. The original developer, Damon Kohler, worked at Google, but SL4A was his own project.
I got the impression that Google weren't thrilled about SL4A on Android, for security, stability and performance reasons, but had no problem with Kohler working on it independently. I'm reading between the lines here though, so could be wrong.
The latest version of SL4A should work on more recent Android versions; you just wont have support for new Android API features.
There was at least one other lead maintainer after Kohler, but development was intermittent for a long time, and ground to a complete halt years ago. I know that they struggled to find Java developers that cared about Python on Android.
The SL4A Google Group still exists. You may still find some support there.
I am new to Eclipse plugin development. I am working to develop a plugin that needs to store large amount of data, as well as search and retrieve from them. I am wondering, if I can use a database for this having plugin dependency. Is there any database engine that comes as Eclipse plugin? I was looking at Apache Derby, but quite unsure about the possibility.
Please suggest.
I have been happily using Derby's Eclipse plug-in for data storage and retrieval. There is a good step-by-step tutorial that assumes very little prior knowledge. Follow these installation instructions, and you should be up and running fairly soon.
Once you get it installed in Eclipse, there is additional useful information. Launch Eclipse and bring up the Help for the Derby plug-ins. Help >> Help Contents>> Derby Plug-in User Guide.
For the Eclipse (Rich Client Platform) it does not matter where or how you store data. It is just a framework which helps deliver a rich client interface.
What other functionality will be required by the users of the data? Apart from getting new data in (is client application the right thing fro that anyway). And searching for certain data? If there is a lot of interaction with the data, draw some possible screens, to get an idea about how it should be implemented in eclipse (eclipse plugins).
There are several plug-ins / extensions which can help you getting the data storage functionality implemented.