Source code toolkit

In February, Richard Bair mentioned in a post that the source code of the Toolbox would become available (http://fxexperience.com/2012/02/a-short-tour-through-javafx-ui-common/). Is that still the case, and when will it be available?
Maybe if I find the time to play with it, I could experiment with it to see if a WebGL implementation would be difficult?
This would make possible scenario to create real-world applications in a modern browser where the DOM is not necessary. One of the scenarios would be GWT and run all the code of java on the client (actually a heavy client compiled in javascript). Or have a version (like jsf) server-side but with only the rendering on the client side (thin client). The client lightweight websockets can be used to send commands to render the server to the client (on business networks latency should not be a problem too). I don't know if it's a good idea or someone else is already busy with her.

All great ideas. Thank you for the patience, sometimes wheels move slowly in a large organization.

I started (and in fact 2 years we have prototyped) the idea of using the dom / svg / canvas / webgl to render on the client FX, as no native window was necessary. It's something I'm very interested for reasons of safety (long story), and also for the user experience reasons (more like a real web application). However, it still requires a plugin because it requires a JVM.

Using GWT works around the problem of the FMV - sort of. You don't always have all of the JRE available, and some semantic case corner is not the same. And GWT can produce large files of JS. But it gets you more or less here.

The application running on the server and sending commands draw down via web shots is another very interesting use cases, in large measure because this action solves the problem of large file GWT. However it will not support the offline sort, shape, or form, so probably it is not really useful in the delivery of web sites to mobile with intermittent connectivity devices (or data caps!).

IF ONLY THE WEB HAD BYTE CODES! We could then bring Java to something compatible semantically rather than JS and then use the browser for everything (networking, graphics, etc.). In other words, treat it as a BONE more some launcher within various operating systems. Really, I think it's the best account approach to all needs and tradeoffs, but GWT is now the closest, we have this idea.

In any case, I hope that we can give more information about OS soon enough. If you were very intrepid, you may decompile the sources and provide your own implementation of glass and pipeline Prism - but I don't know if that goes against any terms of use or anything like that (no idea). And it would really gutsy and courageous and likely to break horribly in the coming months, because we are about to refactor the implementation significantly.

Richard

Tags: Java

Similar Questions

Maybe you are looking for