google-code-export / pyglet

Automatically exported from code.google.com/p/pyglet
BSD 3-Clause "New" or "Revised" License
1 stars 1 forks source link

Add OpenGL version markers in wrapped API calls to track deprecated stuff #590

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. pyglet is slow
2. not because it is Python, but because it's most likely uses outdated OpenGL 
API (that means outdated version)
3. and if you track OpenGL development, most popular version is going to be 
mobile OpenGL ES
4. which is also what WebGL is based on
5. and it is simplified version of previous OpenGL versions (API)
6. meaninig it is stripped version with less garbage and more performance
7. and hardware manufacturers now optimize performance even further for these 
stripped newer versions
8. so pyglet should use these newer API too!

What is the expected output? What do you see instead?
When I run pyglet game, I'd like to know if it uses any outdated OpenGL 
machinery. So I'd like an option to make pyglet print warnings when a call is 
made to a function that is not supported, to say, in OpenGL ES 2.0 or other 
subset.

Original issue reported on code.google.com by techtonik@gmail.com on 20 Jul 2012 at 3:24

GoogleCodeExporter commented 9 years ago
What about using pyglet.gl.gl_info.GLInfo.have_versions?

I'm not sure supporting OpenGL ES is a target for pyglet.

Original comment by useboxnet on 6 Oct 2013 at 7:49