This content has been marked as final. Show 4 replies
Obviously a question for Oracle...
I just want to question your assumption: "our application is complex, and can't be migrated to JavaFX 2.0 in any straightforward way (we want to move to it at some point, but it would take more of a rewrite than a migration)". You are assuming that the JavaFX to Visage move would not be straightforward. My current assumption is that there is a good possibility this particular route will be reasonably straightforward. Do I need to modify my assumption?
Thank you - Chris
Thanks, Chris, I had almost completely forgotten about Visage. Any word on when they're expected to ready for prime time? I'm not sure I want to put all my eggs in that basket unless we're really confident that they're going to have a working product by November at least.
We have not tried Visage out at this stage. My understanding, which mostly comes from the odd post here, is that Visage is a working product that is able to convert small projects. I hope I am not being too optimistic here. Unfortunately, because of the large size of our project, all our eggs are in the Visage basket! Either that or write our own translator. If there are any issues I believe that Steve Chin and his team will be there to help. If you like send me an email at chris the_at_sign strandz the_dot org.
I would like also to know the answers to these questions
Can somebody at Oracle shed some light?
1) Is this allowed? Are we permitted to rehost the JavaFX 1.3 runtimes in a commercial application? 2) Will the current JavaFX certificate expire, making the application unusable at some point? If so, when?