>> Some info here: >> http://marxsoftware.blogspot.com/2010/09/javaone-2010-opening-keynote.html >> and an extract: >> The "high-performance graphics engine" called Prism (and used with >> JavaFX and discussed at last year's JavaOne) will be made available. It >> renders 2D objects today, but will eventually support 3D objects. It will >> support new hardware Accelerated 2D and 3D Graphics Pipeline. This will be >> made available in open source via NetBeans.
This only says that it will made "available in open source via NetBeans". It doesn't say anything about JavaSE support. >> I'm more inclined to wait and see what Prism actually looks like. From >> what I read, it will use DirectX on Windows and OpenGL on other platforms >> - if it is accessible to JavaSE, it would probably be an easier approach >> than wrapping JOGL, for example. > Yes, we have to wait a little to see what to do ... but probably we'll have > to derive our graphic classes no more from AWT, but from Swing or other ... > let's see. We don't currently extend AWT classes. We simply use the java.awt.Graphics2D class for painting. This is something that we would most likely want to change, to use whatever API is provided by Prism. > Ah, on the HTML 5 Canvas, I was speaking on the fact that probably all the > work (not only the graphics part) is in a single thread ... but I could be > wrong, and in any case could not be a problem ... let's see. In HTML, you can actually do some things in a background thread - you just don't have access to the threading API. For example, XMLHTTPRequests will run in the background - it is somewhat similar to Pivot's Task API.
