tom fogal wrote: > arthur m <[email protected]> writes: > >> I have been playing a bit with GLU library in context of 2d >> graphics. I found that GLU tessellator can be improved in regards of >> the interface with very little code added. > > I think you're talking to the wrong community about this. Mesa is/has > just one implementation of GLU, which is a standard specified by the > Khronos group. If you want to change GLU, you really want to propose > your modifications to the standards group, as otherwise your program > will break if the user has a different version of GLU than the one you > hacked on / added your functions to. > > The GLU spec is here: > http://www.opengl.org/documentation/specs/ > Khronos group's website is here: > http://www.khronos.org/ > and information on membership is here: > http://www.khronos.org/members/ > > Though maybe the solution is a new utility library -- the GLU spec > apparently hasn't been updated in 11 years. *shrug*.
Anybody vendor can implement new GL/GLU extensions. Some extensions gain wider support either by promotion to an ARB extension, or are simply picked up by other vendors. Arthur, if you'd like to try to get wider buy-in from the get-go, you could certainly propose your extension to the Khronos group. It always helps though when there's a working example of an extension rather than just a paper spec. I'm OK with using Mesa's copy of GLU as the testbed for this. As for program breakage concerns, there's a GLU extension query mechanism just as there is for GL. Though, there's no gluGetProcAddress() so that could be an issue. -Brian ------------------------------------------------------------------------------ _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
