Posted by gouessej on Feb 11, 2011; 9:44am
URL: https://forum.jogamp.org/Opinions-On-The-JOGAMP-JOGL-Status-Quo-tp2470518p2472337.html

Personally I have not had a lot of problems with JOGL 2 in development phase even on Windows by picking a convenient dev build. Maybe it is a bit early to use it in production. Sven has forgotten to mention that I ported some libraries/API to JOGL 2.0 including Ardor3D, JMonkeyEngine 3 and Nifty-GUI.

Speaking about the status quo of JOGL is a bit insulting on my view and totally wrong, it does not reflect the current situation of JOGL and JogAmp more generally.

JOGL 2.0 is solid enough to work in major projects except that there are some missing features in NEWT (as far as I know, the cursor cannot be removed), the GLJPanel (which has always consumed a lot of memory) is buggier than in JOGL 1.1.1a and disabling the auto swap buffer mode causes an high memory consumption too (which is a real problem in applications that need to display huge meshes).

Best regards

Edit.: My port of Ardor3D is there: http://ardorlabs.trac.cvsdude.com/Ardor3Dv1/ticket/201
My port of JMonkeyEngine 3 is there: http://code.google.com/p/jmonkeyengine/source/browse/#svn%2Fbranches%2Fjme3%2Fsrc%2Fjogl2
My port of NiftyGUI is there: http://nifty-gui.svn.sourceforge.net/viewvc/nifty-gui/nifty-jogl2-renderer/