Robert Osfield wrote:
If GL3 isn't providing any gl_ uniforms surely they can't be reserved,
you can only reserve something if it might exists. I can see why gl_
will be reserved for GL2, but I can't see the issue for non backwards
compatible GL3.
Hi again, Robert. If you really must use the "gl_" name for matrix
uniforms, then perhaps OSG's path forward for GL3 is to use the
compatibility profile, which preserves all that old GL1/2 stuff. But it
won't be "real" GL3 if you take this approach.
I know that I personally have clients that are looking to minimize
disruption as OSG moves to GL3. On the other hand, GL3 is a new API and
it seems like the best way for OSG to move forward is a clean break. If
we are indeed going to branch OSG for GL3, then perhaps the best
solution is to have the community maintain both branches. Apps on oldOSG
would port to newOSG as they see fit, (with changes such as matrix
uniform names). The old branch would continue to not just exist but also
improve and grow, as long as the community continues to support it.
This seems like it would be less work than trying to continue to support
all the features deprecated in GL3.
-Paul
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
