> > Modern Python techniques suggest a context manager (or set of related > context managers that could be used individually or combined) that > pushes/pops state :-) >
Indeed, I currently use them as a context manager myself, which you've probably seen from the __enter__/__exit__ methods in the classes. In any case, I think this is something that can get sorted out after the model stuff is in. Perhaps attach some GLSL to the model to handle transformation? ModelGroup > etc. then just loads the vertices etc. and manages the GLSL variables. > I was thinking of just using legacy OpenGL transforms for the time being on the Model class, since I'm not familar with 2.X era GLSL. That said, I do have another branch in which I've been experimenting with re-writing pyglet's core to be based on OpenGL 3.3+. So far I have the image and graphics modules ported, and simple Shader/ShaderProgram classes. It would be easy enough to update the ModelGroup at a later date when we decide to tackle that update... That's an entirely different discussion! -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
