Posted by gouessej on Mar 04, 2011; 9:40am
URL: https://forum.jogamp.org/WebGL-specification-1-0-is-final-and-also-WebCL-tp2631673p2632166.html

Hi!

This is not the way to go as WebGL won't be supported by Microsoft Internet Explorer and JavaScript is not as fast as Java which means that applications ported from Java + JOGL to HTML5 + JavaScript + WebGL would be noticeably slower. Maybe some efforts could be done to allow the use of WebGL in GWT but in my humble opinion, it is not the matter of JOGL. JOGL has only a few contributors; if you really want to use JOGL with WebGL, feel free to contribute. On my view, we should not waste any time with platforms and devices that are not open enough, that is why I don't try to use Java on iphones and consoles.

I'm only a "small" contributor, I consider that the priorities consist in having a stable version of JOGL 2 providing at least the same services than JOGL 1.1.1a and providing a full and reliable implementation of new features that have already been announced (especially NEWT). Maybe the extension of NEWT for SWT could be "experimental" in JOGL 2.0 and become more reliable and complete in JOGL 2.1. Android support would be easier to implement than WebGL support and maybe more useful as Android supports Java.

Java 1.7 will provide an AWT-less or AWT-free plugin for applets which will have a very short startup time (less than one second). Therefore, focusing on pure Java solutions in the browser is a good option instead of using WebGL that is still not implemented in Microsoft Internet Explorer. I rarely use NEWT, I don't know if it is possible to use it in applets without any AWT or Swing component.

As Michael said, web is only a possible scenario of deployment.