For those using JOGL with Java 5.0 what is the experience? I was looking at the concurrency utilities, high-res timer, and generics. Would you say it is stable enough to not be more pain than value? Does it play well with JOGL, and Eclipse 3.1?
I’ve been using Java 5.0 for about 5 months now.
I switched to Eclipse 3.1 from the M2 build onwards
to get the new Java 5.0 features within the IDE.
JOGL was used throughout this process. It’s all
been working like a charm, even when I have to
use JNI alot (with VS.NET). System.nanoTime() is
a blessing and looking into the source release of
JDK5 confirms that it is using QueryPerformanceCounter()
on Win32. However, just be aware of the known
issue of QPC sometimes skipping ahead on certain
chipsets, esp mobile ones. There’s a MSDN article
on this very issue. I use threading a lot and so
I use some of the concurrent containers, esp
ConcurrentLinkedQueue and it works beautifully.
.rex
We have been using 5.0 since the first betas without any problems.
// Tomas
If you are going to develop JOGL for Java 5 then I’d recommend you wait. You can not run Java 5 applications on the Mac. There is only support for JDK 1.4.2, and I don’t know of a timeline for when Apple will come out with support for Java 5.
[quote]If you are going to develop JOGL for Java 5 then I’d recommend you wait. You can not run Java 5 applications on the Mac. There is only support for JDK 1.4.2, and I don’t know of a timeline for when Apple will come out with support for Java 5.
[/quote]
Apparently its in the OSX Tiger which is released in 14 days (although I cant confirm this is correct), so I wouldn’t worry too much about this issue. As for older versions of OSX I am told that you can copy the tiger version straight into the older versions of OSX, so I see no reason why it wont be properly released for older versions soon.
It has been stated on the Java-dev list from Apple that 1.5 will require Tiger. I do not think they have any intention of making it available on older releases. There may even be technical reasons for that. They are probably using Tiger only API calls to support things like the new concurrency package, and accelerated graphics, etc. I have a select membership, so I am tracking things, but can not say anything. The Tiger page lists 1.4.2 for Java so I do not believe 1.5 will be in 10.4.0. Here is hoping for 10.4.1 or 10.4.2.