Thank goodness they chucked out the pointless fx script for regular java syntax.
Sounds like javafx 2 is just a lighter weight java with a new graphics backend, chucking out the bloat of awt, swing and java 2d. Yay!
Prism is built on DirectX, OpenGL and has a software fallback. I don’t think you will have direct access to what’s under Prism. But now that its a standalone Java library I’m sure someone will hack it.
JavaFX is the scenegraph. If you’re not using it for rendering then you’re not really using JavaFX. You probably mean the new AWT-less plugin with other windowing system. Well, maybe that’ll be possible, too, but I think that LWJGL/JOGL would have to adapt to use JavaFX’s windowing, if some direct access to it is provided.
Hmm, kinda like the Java2D/JOGL integration? I doubt this will be possible without help from Oracle. They’ll need to expose their OpenGL context, won’t they?
This release will have pretty much all the features that we had in JavaFx 1.3
We have the Web-view which is one of the things that people have been waiting for forever; essentially it’s an embedded web browser; we will have the ability to modify the DOM in the browser; or attach listeners to it so you can get callbacks and handle it in java and so forth;
We also have 3D so in the current release we’ve got 3D transforms such as translating in the Z or rotating about a different axis. However in a followup release, the one after 2.0, we will have 3D primitive shapes and more support for 3D animations and so forth.
There’s a couple of different ways that you can deploy on desktop right now; we have the ability to do executable jars. You can also run it, you know, from your IDE or from the command line just like any other normal java application; as well as through JNLP and so forth. Now in EA and JavaFx 2.0 one of the big features that we have is are new hardware accelerated graphics platform that we call Prism. And Prism runs without any support on Swing or AWT which can really help out on our startup time and performance. However that requires changes in the plug-in to be able to do that because the normal java plug-in is AWT based. So there is a lot of work going into Java 7 plug-in in order to allow you to have an AWT-less or non-AWT plug-in implementation. So that will be going out with Java 7 but in the mean time what that means is until that is into proper circulation we aren’t able to run the full hardware accelerated Prism inside of a browser. So at the time of EA, we are not going to be supporting running javafx in the browser but by the time we get to Beta you will be able to run javafx inside the browser.
Seems that Applet support will need Java 7 and 3D animations will be coming (but not quite yet.)
This topic seems to be completely the opposite of the ‘doors are closing’ one, even in regards to my own personal opinions on Java. It sounds like Oracle is doing everything right with Java and we’ll be getting new, fast, powerful stuff to use for client-side Java in the near future. Awesome!
I know, but it was done by Sun, and required Java2D to expose its OpenGL pipeline. I believe Oracle would have to do the same with JavaFX (expose the OpenGL pipeline) in order for the integration to be possible.