Release 2.3.1: GlueGen, JOGL[OculusVR SDK 0.4.4 w/ DK1 + DK2], misc..

Planned release 2.3.1:

<http://jogamp.org/wiki/index.php/SW_Tracking_Report_Objectives_for_the_release_2.3.1>

- GlueGen: Bug 1149
  - Using JCPP instead of PCPP, allowing complete macro handling

- JOGL: Bug 1150
  - Fix GLContextImpl.createImpl(..)
    NoARBCreateContext and '!ARB GL >= 3.1' issues

- JOGL: Bug 1147/1148:
   - Using unique monitor device ids on X11 and OSX
   - Fix XRandR13 Usage: Rotate / Change-Mode

- JOGL: Bug 1116
   - Add OculusVR DK2 Support (via SDK 0.4.4)

Above major changes are quite stable:
  - currently in autotest

+++

Warning:

Even though *shall* be a 100% backward compatible release,
API changes were necessary for Bug 1116 (OculusVR DK2)
within package 'com/jogamp/opengl/util/stereo/'!

See <http://jogamp.org/git/?p=jogl.git;a=commit;h=b142c7130c05c9c0ae97841b4ff626f528c45438>.

Otherwise, this release is API compatible and can be used
as a drop-in replacement!

+++

<http://jogamp.org/wiki/index.php/SW_Tracking_Report_Objectives_for_the_release_2.3.1>


Cheers, Sven

Released: <https://jogamp.org/wiki/index.php/Release_2.3.1>

Mark is working on a maven central push.
Our jogamp maven repo already contains 2.3.1.

Please note that building from source has changes slightly:
  GlueGen:

/home/dude/projects/jogamp> git clone --recurse-submodules git://jogamp.org/srv/scm/gluegen.git gluegen

The GlueGen source must be fetched using -recurse-submodules, which imports JCPP, now used as the default C preprocessor.

See: <http://jogamp.org/gluegen/doc/HowToBuild.html>

I have updated JogAmp's Ardor3D Continuation so that it uses this release:
https://github.com/gouessej/Ardor3D/commit/2ca7f3ed8bb716771484e0a2c1cf4233e414f561

I have updated Java3D 1.6.0 pre so that it uses this release:
https://github.com/gouessej/java3d-core/commit/264608060948a634b53a13ee96ed07527eb07340
I'm going to update its build instructions.

Another contributor will update LibGDX to make it work with Xerxes' changes and this release. I still have to update JMonkeyEngine 3 (I don't know yet whether I will implement a renderer for its new unified rendering system).

On 03/30/2015 09:59 AM, gouessej [via jogamp] wrote:
> I have updated JogAmp's Ardor3D Continuation so that it uses this release:
> https://github.com/gouessej/Ardor3D/commit/2ca7f3ed8bb716771484e0a2c1cf4233e414f561
>
> I have updated Java3D 1.6.0 pre so that it uses this release:
> https://github.com/gouessej/java3d-core/commit/264608060948a634b53a13ee96ed07527eb07340
> I'm going to update its build instructions.
>

KUDOS!

> Another contributor will update LibGDX to make it work with Xerxes' changes
> and this release. I still have to update JMonkeyEngine 3 (I don't know yet
> whether I will implement a renderer for its new unified rendering system).

Sounds great.

Thank you Julien!

~Sven

Sven Gothel wrote

Sounds great.

Thank you Julien!

You're welcome. I admit that I don't understand the moves of some constants and some changes of return types (long to int?) in the ARB methods for the shaders.

gouessej wrote

I'm going to update its build instructions.

Done:
http://gouessej.wordpress.com/2012/08/01/java-3d-est-de-retour-java-3d-is-back/#howtobuildthelibrary

gouessej wrote

Another contributor will update LibGDX to make it work with Xerxes' changes and this release.

I did most of the changes:
https://github.com/gouessej/libgdx/commit/a2aed9a3d035e29aff7a7fdf235a89585a925cb4
https://github.com/gouessej/libgdx/commit/35f92d02455e327f9cc0801a4b87d4df438f3d33
https://github.com/gouessej/libgdx/commit/b44dfbb89175e549ae5d31fa32cdd6fcd6232fd9

I updated jogl, now it cant find GL3 anymore in

import javax.media.opengl.GL3;

rather it finds it in

import com.jogamp.opengl.GL3;

why?

I had to go back to 2.2.4 to fix it

elect wrote

I updated jogl, now it cant find GL3 anymore in

import javax.media.opengl.GL3;

rather it finds it in

import com.jogamp.opengl.GL3;

why?

I had to go back to 2.2.4 to fix it

The 2.3 release is not backwards compatible (as you noticed). The reason for the package change is documented in the bug report.

https://jogamp.org/bugzilla/show_bug.cgi?id=682

Hope that helps.

jmaasing wrote

elect wrote

I updated jogl, now it cant find GL3 anymore in

import javax.media.opengl.GL3;

rather it finds it in

import com.jogamp.opengl.GL3;

why?

I had to go back to 2.2.4 to fix it

The 2.3 release is not backwards compatible (as you noticed). The reason for the package change is documented in the bug report.

https://jogamp.org/bugzilla/show_bug.cgi?id=682

Hope that helps.

Thanks for clarification and for the link, jmaasing

I will then upgrade all my projects to the new jogl

elect wrote

I updated jogl, now it cant find GL3 anymore in

import javax.media.opengl.GL3;

rather it finds it in

import com.jogamp.opengl.GL3;

why?

I had to go back to 2.2.4 to fix it

There is no reason to panic when we move some classes into another package and I don't understand why you preferred switching back to JOGL 2.2.4 initially instead of accepting this change. Moreover, I gave some links to some change sets showing that I simply edited some imports, I didn't switch back to JOGL 2.2.4. We don't randomly move classes but I can understand that you don't expect such change from a minor release.

gouessej wrote

elect wrote

I updated jogl, now it cant find GL3 anymore in

import javax.media.opengl.GL3;

rather it finds it in

import com.jogamp.opengl.GL3;

why?

I had to go back to 2.2.4 to fix it

There is no reason to panic when we move some classes into another package and I don't understand why you preferred switching back to JOGL 2.2.4 initially instead of accepting this change. Moreover, I gave some links to some change sets showing that I simply edited some imports, I didn't switch back to JOGL 2.2.4. We don't randomly move classes but I can understand that you don't expect such change from a minor release.

I didnt panic and I didnt prefer to switch back, I just thought it was an error of the new builds

As I wrote, I plan to upgrade all my project to the new jogl sooner or later

elect wrote

I just thought it was an error of the new builds

It's a bit farfetched as the commits I showed use the new package locations... Anyway, let us know whether you find any regression when switching to JOGL 2.3.1. Sorry for the misunderstanding.