Tom Schindl tom.schindl at
Thu Oct 10 13:41:33 PDT 2013

So when I compile my own FX what target to I compile to? I guess I
compile on linux, right?


On 10.10.13 22:01, Tomas Brandalik wrote:
> 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.tiffeau at>:
>>> 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.

More information about the openjfx-dev mailing list