GL3 and 3.1 support has been recently commited in svn
https://jogl.dev.java.net/source/browse/jogl/branches/JOGL_2_SANDBOX/make/config/jogl/gl-gl3.cfg?rev=1919&view=markup
about time :-*
yes it is 
Hi!
It is an excellent piece of news ;D I’m impatient to see the official release. JOGL is not dead, it rocks Thank you for your efforts.
(just to prevent confusion) i only pressed update yesterday - that weren’t my efforts
the cool thing about the GL3x support is actually: the build uses the new gl3.h header file which has been released around 3 weeks ago, this means the GL3 binding is directly generated from spec (no handcoding or third party mesa headers).
Thank you, that you like it.
So, on Linux with the NVIDIA 180.37.05 driver it works fine,
you can verify the instantiation with ‘java demos.GLInfo -GL3’
As you can see in the generated javadoc, GL2, GL3 and ES2,
all share GL2ES2 as their common subset to write kind of compatible
code …
OpenGL 3.0 is available within GL2 (you know, the extensions)
where 3.1 finally is exposed with GL3 in a forward compatible fashion only.
I guess that’s what we want … get rid of the ole crap 
Have to test on Windows … well, and MacOSX … when it’s ready.
Have fun …
Reviews … ideas … shoot.
yes that was the right decision. (far better than the overengendered interface hierarchy I proposed via email)
I am using a modified gluegen to generate all deprecated functions as @deprecated and noticed that the GL3 interface (->the forward compatible context) still has a handful of deprecated functions (e.g glHint(…)). But this is probably not your fault - i guess its rather a inconsistency between the new gl3.h and the spec. (however i guess calling those functions would cause a gl error -> GLException)
anyway good work!
(sad that i wasn’t able to convince you to move directly to java 1.5 syntax )
Yes, glHint is in the GL/gl3.h from May 05 2009
and in the forward compatible spec (revised) glspec31.20090528.pdf
from May 28 2009 - both available on
http://www.opengl.org/registry/
Just double checked - so it’s all good
However … if a new revision is coming out … we will update it … sure.
EDIT: BTW … since GL3 includes ES2, not having ‘Hint’ would make live a drag
The ‘family’ tree is still there … having GL2ES2 as our common denominator for GL2 ES2 and GL3,
and this is strongly intended
Java 1.5 syntax … well, you know, we want to provide a wrapper for OpenGL profiles
available on all platforms, including mobile/embedded devices having only a JVM with Java 1.3
So … the little inconvenience in the JOGL implementation will serve the bigger audience.
Thank you for your valuable input and discussion we had,
it always helps to brainstorm those thing … of course.
The next remaining cleanup is to put the GL profile selection into GLCapabilities,
since it is possible and intended to have a GL2 and a GL3 context running in the same
application - if it’s supported. So the static selection in GLProfile will go away
and it will merely serve as a profile helper class.
Reasoning: More flexibility, prepare for other native profiles (OpenCL, …), hence bug free.
GLCapabilities, because we need to know the desired profile through the whole factory chain,
GraphicsConfig - Drawable - Context.
Semantics: We may fall back to a compatible one, ie GL2, GL3 or ES2 if GL2ES2 is selected.
I was making this joke … ‘JOGL is family oriented’
If you see any fraud in the architecture, especially if we break features and the spec,
please notify us. Yes, the JOGL2 branch will be promoted to JOGL within a short time.
Wow this is good news! Slow arriving, but very welcome!
However, I think you guys are going to have to spend alot more time with the community to restore some confidence in JOGL. I’m sure you’ve lost a lot of followers with the long absence and lack of updates.
Anyway, thankyou for not totally abandoning us
If in any doubts … have a look at the commits …
New SVN: https://jogl.dev.java.net/servlets/SummarizeList?listName=commits
Old CVS: https://jogl.dev.java.net/servlets/SummarizeList?listName=cvs
The ‘community’ thing, well, I have to admit, I hate forums
and love mailinglists.
I know, we had this discussion a few month ago …
May I vote for the mailinglist?
Seeing Google’s new ‘Wave’ demo … well, is there any mailinglist/forum
wrapper ? At least the ML is archived … well.
However … there is always an email address to wake us up
Feel free to do so …
+1 for lists. A project without a mailinglists is IMO only a visioning repository
btw if you could move the project (+visioning history) to kenai we would even have a chat for free (and the mailinglist/forums are also better integrated).
I still don’t buy this argument
are phones/handhelds out there which are capable to run OpenGL-ES but rely on Java 1.3? Even JavaFX compiles into java 1.5 bytecode (Annotations etc). All vm’s/compilers i tried to experiment on phones like the iphone ran flawlessly with java1.5. (e.g jikesvm, xmlvm crosscompiler…)
…running applets with pre 6u10 JREs isn’t recommented anyway
and in worst case there is still the retroweaver project
are phones/handhelds out there which are capable to run OpenGL-ES but rely on Java 1.3?
Definitely yes.
JavaFX is another story
Yes, they utilize the retroweaver project, but why making life so complicating
and even adding another layer of obfuscation to embedded platforms where no
true benefit is visible?
Generics/templates etc cannot really benefit the user API of JOGL, AFAIK.
And only a very useful public API feature of Java 1.5 could convince us to allow
such change of platform requirements or obstacles.
The way we implements things is not so much important here, as long
we are only talking about convenience and not quality.
Let’s start a JOGL Java 1.5 flamewar thread
Are the nightly builds going to be restarted soon? I’d like to look at the new stuff, but find working from the sources to be a pain. It took alot of effort to build last time I tried because the ant files were out of date. Or are there some beta binarys around?