Hi Tomas,
today, I took the time to investigate a little more time on this. 1. I build an entirely new openjfx78 build for android 2. starting this gave me several errors that lead me to the conclusion that I need a java6 openjfx 3. based on openjfx78 I ported it back to java6 (adapted gradled scripts, and tons of java source code) 4. Now it's almost running on an 18th android. All libraries are firing up until the CssStyleHelper is called with a static call to createStyleHelper. That looks like the font stuff is not in jfx78. That's why "new Font" returns with null and therefore CssStyleHelper crashes. Do you have any idea how to proceed? Do I really have to port JFX8 from Java8 back to Java6 to get a full flegded JFX8 running on Android? That would be pretty heavy it took me nearly 10 hours to port jfx78 to Java6 (without Ensemble). I am willing to contribute, in case we've got a development direction. kind regards Matthias Am 11.10.2013 um 07:51 schrieb Tobi <t...@ultramixer.com>: > Is this standalone vim working with JIT? Does it works well? > > We recently tried to use the embedded version of oracle JdKs com Linux/ARMv7 > soft float on Android but if doesn't work because if missing linked dylibs on > Android..,. > > >> Am 11.10.2013 um 06:52 schrieb Tomas Brandalik <tomas.branda...@oracle.com>: >> >> COMPILE_TARGETS=android >> Good, then use FX78 and you can give it a try. I have my local fork of >> javafx for testing DalvikLauncher. Standalone Vm for Android is not >> available for download. >> >> -Tomas >> >>> FX78 should be compatible with Java6 because RoboVM is built on dalvik >>> classlib and JavaFX works there! >>> >>> Tom >>> >>>> On 10.10.13 22:42, Tobi wrote: >>>> Hi Tomas, >>>> >>>> How did you test the Dalviklauncher? Do you have a Java6 compatible jFX >>>> version? >>>> >>>> And how did you test the JavaSELauncher? Do you have a JVM for android? >>>> Where can we download it? >>>> >>>>> Am 10.10.2013 um 22:01 schrieb Tomas >>>>> Brandalik<tomas.branda...@oracle.com>: >>>>> >>>>> Hi Tobi and Philippe, >>>>> Android port is being developed in open source so all developers can see >>>>> every progress. There is nothing to hide. You can understand it as an >>>>> example of porting javafx runtime to a linux based platform not a product >>>>> with a roadmap. >>>>> As you've noticed there are 2 launchers DalvikLauncher and >>>>> JavaSELauncher. Have a look at DalvikLauncher it is quite simple how it >>>>> launches an application. What you need to try it out is an java6 (dalvik >>>>> vm limitation) compatible javafx fork. >>>>> On the other hand JavaSELauncher uses standalone vm which is not part of >>>>> the port. It expects that the vm is packaged with an apk. The launcher >>>>> unpacks vm, installs it, setup classpath, main class debug port etc (all >>>>> specified in manifest) and launches it . These are the 2 options which >>>>> can be further extended by the community. >>>>> >>>>> best regards >>>>> -Tomas >>>>> >>>>>> On 10/10/2013 06:10 PM, Tobias Bley wrote: >>>>>> Tomas from Oracle is working on the Android port of JavaFX. He has >>>>>> developed a DalvikLauncher and a JavaSELauncher. So he is able to tell >>>>>> you (and me :)) more about that important theme „JavaFX on Android“. >>>>>> >>>>>> Best regards, >>>>>> Tobi >>>>>> >>>>>> >>>>>>> Am 10.10.2013 um 16:55 schrieb Philippe >>>>>>> TIFFEAU<philippe.tiff...@steria.com>: >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> Someone can make a clear answer about JavaFX on ANDROID ? >>>>>>> >>>>>>> If it works how to use ? Otherwise the roadmap is .... >>>>>>> >>>>>>> Best Regard. >>>>>>> >>>>>>> This email and any attachments may contain confidential information and >>>>>>> intellectual property (including copyright material). It is only for >>>>>>> the use of the addressee(s) in accordance with any instructions >>>>>>> contained within it. If you are not the addressee, you are prohibited >>>>>>> from copying, forwarding, disclosing, saving or otherwise using it in >>>>>>> any way. If you receive this email in error, please immediately advise >>>>>>> the sender and delete it. Steria may monitor the content of emails >>>>>>> within its network to ensure compliance with its policies and >>>>>>> procedures. Emails are susceptible to alteration and their integrity >>>>>>> (including origin) cannot be assured. Steria shall not be liable for >>>>>>> any modification to a message, or for messages falsely sent. >>
