JavaFX port to iOS/Android status

[Niklas Therning]

RoboVM reuses quite a lot of code from Android and Dalvik. As long as they
don't support the required Java7/Java8 features I don't think RoboVM will
either, at least not with the man-power I have at the moment (only me! :-)
). IIUC JavaFX8 is supposed to be feature complete in 10 days and given
that the switch to requiring Java8's compiler was announced only a few days
ago I assume that not that much invokedynamic and other stuff not supported
by RoboVM will make it into JavaFX8. So for the short term it could be
feasible to maintain a branch with these features backported to work on
RoboVM.


On Mon, May 13, 2013 at 1:37 PM, John C. Turnbull <ozemale at ozemail.com.au>wrote:

> OK, thanks for the info.
>
> Now that I am talking directly to the creator of RoboVM, what is your view
> on supporting invokedynamic in RoboVM?  I ask because I believe code is
> being added to OpenJFX as we speak that makes use of this new bytecode and
> it is thus going to be crucial that RoboVM supports it if JavaFX 8 is to
> run
> on iOS etc.  This is the version (to be released with Java 8) that is the
> main version that I see the JavaFX community wanting to run on mobiles and
> tablets.
>
> Thanks,
>
> -jct
>
> -----Original Message-----
> From: openjfx-dev-bounces at openjdk.java.net
> [mailto:openjfx-dev-bounces at openjdk.java.net] On Behalf Of Niklas Therning
> Sent: Monday, 13 May 2013 21:26
> To: openjfx-dev at openjdk.java.net
> Subject: Re: JavaFX port to iOS/Android status
>
> The choppiness is likely due to the fact that RoboVM hasn't been optimized
> for speed at all yet. E.g. virtual/interface method dispatch is horribly
> slow at the moment. I hope I'll be able to focus on performance shortly but
> right now the focus is on compatibility and stability.
>
>
> On Mon, May 13, 2013 at 12:27 PM, John C. Turnbull
> <ozemale at ozemail.com.au>wrote:
>
> > Niklas, this is *awesome* work, thanks very much on behalf of the
> > JavaFX community.
> >
> > It is very promising that so few changes were required to get things
> > working.  One thing I noticed in the video was that BrickBreaker
> > animation performance was a bit choppy i.e. not smooth.  Is this a
> > symptom of the video itself or does JavaFX run like this on iOS?
> >
> > Of course I realise that it's only *very* early days so I am sure
> > performance issues can be improved with prudent optimisation.  I am
> > just curious to know whether the video gives an accurate picture of
> > what's really happening...
> >
> > Anyway, this is the best news I have had in ages!  Keep up the great
> work!
> >
> > Cheers,
> >
> > -jct
> >
> > -----Original Message-----
> > From: openjfx-dev-bounces at openjdk.java.net
> > [mailto:openjfx-dev-bounces at openjdk.java.net] On Behalf Of Niklas
> > Therning
> > Sent: Monday, 13 May 2013 19:37
> > To: openjfx-dev at openjdk.java.net
> > Subject: Re: JavaFX port to iOS/Android status
> >
> > Hi,
> >
> > I'm the founder of the RoboVM project. Yes, RoboVM uses AOT and yes
> > that's a real iPad in the video.
> >
> > /Niklas
> >
> >
> > On Mon, May 13, 2013 at 11:07 AM, Tobias Bley <tobi at ultramixer.com>
> wrote:
> >
> > > Great to see! Does it mean RoboVM uses AOT to compile the complete
> > > OpenJFX to native code? Does it work on a real iPad too?
> > >
> > >
> > > Am 13.05.2013 um 10:51 schrieb Tom Schindl
> > ><tom.schindl at bestsolution.at
> > >:
> > >
> > > > On 21.04.13 20:12, Tom Schindl wrote:
> > > >> Hi,
> > > >>
> > > >> I think Richard mixup a bit in his list VMs and AOT compilers.
> > > >> XMLVM is a AOT compiler producing an iOS/Android executable from
> > > >> Java-Class files (in the end it produces ObjectiveC code which
> > > >> emulates the Stack of the JVM so the code is not really human
> > readable).
> > > >>
> > > >> There are 2 stragegies to run FX on iOS (fairly the same is true
> > > >> for
> > > >> Android):
> > > >> * get a VM running on the device (this VM is not allowed to JIT)
> > > >> * AOT compile your Java app so that it runs without a JVM
> > > >>
> > > >>
> > > >> I currently only know of Avian to run as a JVM on iOS/Android
> > > >> whereas there are at least 2 AOT compilers:
> > > >> * XMLVM
> > > >> * RoboVM (main target is iOS as of now)
> > > >
> > > > http://blog.robovm.org/2013/05/javafx-openjfx-on-ios-using-robovm.
> > > > ht
> > > > ml
> > > >
> > > > Tom
> > >
> > >
> >
> >
>
>