Posted by Cyrille on Jul 29, 2010; 8:15am
URL: https://forum.jogamp.org/Ease-backwards-compatibility-with-JOGL-1-x-apps-tp1003131p1003766.html

Hi,

I understand the need of easing backward compatibility with JOGL 1 apps in order to make experimenting or benchmarking more straightforward.

But I completely disagree with the proposal that states that the default of JOGL 2 should be to mimic JOGL 1:
- using GL2 as a default profile for GLCapabilities would satisfy the backward compatibility issue but would not be acceptable in the long run.
- using GL as an alias for GL2 would not help to make the API clearer. Anyway, I guess that this API is governed by the JSR-231 and that Jogl's designers do not have the direct capability to change it.
- JOGL 2 is designed to be open to the future of OpenGL. Jailing it in legacy specifications does not comply with this goal.

Another way to achieve the straightforward compatibility without polluting JOGL 2 forever could be to implement a compatibility (and therefore optional) package in a separate JAR that would provide classes and interfaces that would make JOGL2 look like JOGL 1. For instance a GL interface in this package could inherit GL2. This is an idea but I guess that implementing this would be quite bothersome and time consuming. In my opinion, JOGL 2 is today much more lacking stability than this backward functionality.

I just wanted to give a counterpoint.

Thanks,
Cyrille