Are we facing an Oracle iron curtain on this. Can you really not just tell us what VMs you've 'seen' it run on?
On 06/07/2013, at 12:35 PM, Richard Bair <richard.b...@oracle.com> wrote: > Testing is a strong word. I'd say we have seen it work. > > On Jul 5, 2013, at 12:51 PM, Daniel Zwolenski <zon...@gmail.com> wrote: > >> You guys have obviously had jfx running on both ios and android internally >> before for demos (and I assume you're testing this code you're releasing?). >> What JVMs are you using for this? >> >> Niklas I'm assuming that robovm used the android base because j8 features >> are either not possible or much more work to support. Is this the case or >> was there another reason for that choice? I'm assuming that at best moving >> to j8 is not a trivial or quick task? >> >> Making the backport fully android focused would seem like the shortest path >> for both ios and and android here? It's not great that there's so much to >> change in jfx for this to work. Apart from the extra hassle/delay now, this >> is going to make maintaining this backport and keeping it inline with bug >> fixes and updates messy. >> >> >> >> On 06/07/2013, at 12:42 AM, Richard Bair <richard.b...@oracle.com> wrote: >> >>> We have implementations for Android and iOS that are both functional on a >>> Java 8 VM. It looks like, because the iOS one is so closely related to the >>> Mac build, it was the easiest one to get a build for the open community. >>> We're working on the Android build scripts. The situation on Android is >>> exactly the same as iOS -- we're open sourcing the library code, but not a >>> Java 8 VM. I would expect that if the iOS build on RoboVM works, that the >>> Android build for RoboVM would also work, but I haven't tried it. >>> >>> Richard >>> >>> On Jul 5, 2013, at 5:07 AM, Daniel Zwolenski <zon...@gmail.com> wrote: >>> >>>> Thanks Niklas - sounds like there's still a bit to do. >>>> >>>> I'm still a bit confused though, I thought the JFX team were/are giving us >>>> a version of jfx that is specifically designed to work on Android but it >>>> sounds like that's pretty far from the actuality? What will the gradle >>>> build for android actually give us? >>>> >>>> I'd be keen to hear from someone on the jfx side on all of this. Is this >>>> how you planned for your smart device releases to work or has something >>>> gone wrong in the journey here? >>>> >>>> >>>> >>>> On 05/07/2013, at 9:57 PM, Niklas Therning <nik...@therning.org> wrote: >>>> >>>>> <mime-attachment.txt> >>>
