"If the lessons of history teach us anything it is that nobody learns the lessons that history teaches us."
More pages: 1 2 3 4
OpenGL 3.2
Saturday, August 8, 2009 | Permalink

Having been on vacation I'm a bit late to the party, but OpenGL 3.2 has been released and the specs are available here.

I like the progress OpenGL has made lately and it looks like the API is fully recovering from the years where it was falling behind. If Khronos can keep up this pace OpenGL will remain a relevant API. I hope the people behind GLEW and GLEE get up to speed though because neither have implemented OpenGL 3.1 yet. In the past I rolled my own extension loading code, but was hoping to not have to do that and use libraries like the above. Looks like I might have to do my own in the future as well just to be able to use the latest and greatest.



Enter the code below

Vilem Otte
Friday, August 14, 2009

# 2) readability
VBOs or dl or VAOs ... everything can me written as readable text or as code-dump ... as long as you don't have to use SIMD and very cruel ways to get higher performance (don't count too much OpenGL coding here), let our sample here don't be high performance SAH KD builder in O(N log N).

# 3) simplicity
VBOs are same simple as dl or VAOs (or glBegin/glEnd ) and can be written readable (beginner just has to be less lazy to read good tutorial on it)

Sunday, August 16, 2009

Keep in mind that Kronos released two 3.2 specs: core and compatibility; the compatimbility profile contains all those bits: display lists, immediate mode, etc. Oddly, now I think writing a GL driver is nastier now because functionally, a hardware manufacturer has to really provide both a core and compatibility profile.

For the immediate mode, fixed function pipeline and display lists, the correct place is a user space library on top of GL, I'd love if GLU got some attention as it is in need of some love too. It would be possible to make a GLU specification, for OS vendors (or something) which has:
1. fixed function pipeline emulation (for teaching purposes)
2. immediate mode emulation
3. display list emulation

and whatever else. would be nice if GLU go updated (mostly for teaching) to provide standard matrices and standard 3D ops (i.e. analogues of glTranslate, glRotate, glFrustum) which modified a matrix in memory...

More pages: 1 2 3 4