On 10/2/07, Andrew Lentvorski <[EMAIL PROTECTED]> wrote: > Bob La Quey wrote: > > Specifically from Python. > > It's been a while, though. > > > I am finding odd dependencies which I do not > > understand between OpenGL.GL, OpenGL.GLUT, > > OpenGL.GLU and glFreeType. > > Welcome to SWIG Hell. PyOpenGL is a prime example of what I hated about > SWIG.
Hmm ... maybe I should go through things in C first. I am a much better C programmer anyway. Then once I actually understand OpenGL I can worry the issues of Python. I suspect that there are underlying data structures that various members of the API compete for in ways that I do not understand. BobLQ > I found that using PyGtk and PyGtkGLExt were the most effective method a > couple of years ago. Unfortunately, it looks like GtkGLExt is now > unmaintained. :( > > You can avoid the whole GLUT system (and I recommend that you do so > because it really kinda sucks) because you use the PyGtk system for > menus and widgets while PyGtkGLExt gives you a managed OpenGL frame in > which to draw using OpenGL. > > IIRC, I dodged the whole SWIG garbage by using ctypes in Python to > access the OpenGL API and directly draw on the frame returned by PyGtkGLExt. Yeh. After I do the C thing that migh be the way to go. > The NeHe tutorials are probably more instructive. However, they > generally have a high Windows-centric focus in spite of being OpenGL: > http://nehe.gamedev.net/ There is a Python version for pyopengl. That is what I started morphing. Then I get these unexpected interactions ... > Good luck, > -a Thanks, I think I need it. BobLQ -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
