Pyglet is a great library but two little details bother me in a very big way. I really wish that alpha transparent blitting and 2D rotation were built into the high-level image API. I use these two features extensively in my 2D game prototypes, and it is very annoying not to have them readily available through an argument to a method call.
I have seen a number of other posts in pyglet-users asking about alpha transparency and rotation, and I think it's not really enough to tell them to use the OpenGL functions to get the effects. These basic effects should be built into the high-level API. I strongly feel that it should not be necessary to "drop down" to OpenGL for these two very common use cases. The mental context switch from nice pythonic Pyglet to C-based OpenGL is jarring and unnecessary. I know that Pyglet 1.0 is now in beta and feature frozen. I agree that the focus for the beta should be working out the bugs to get it ready for a final release. But the two issues I mention above should be a major consideration for 1.1. Pygame has alpha (and colorkey) transparent blitting through the Surface object, and rotation through the transform module. Pyglet should probably support these features in a different way. I think one convenient and non-disruptive (to the current API) way of supporting alpha transparency is to give PNG images alpha transparency by default (if there is an alpha layer present). The most common use case I've seen is to create a transparent PNG in GIMP, load it into Pyglet, and then exclaim "WTF?!" when it doesn't show transparency. Transparency based on file type given to image.load would go a long way towards making Pyglet more fun to use. I think rotation should be handled by adding a "rotation" optional argument to AbstractImage.blit (for example: img.blit(x=50, y=100, rotation=45). And rotation should be in degrees. In my opinion, these two very simple changes would make Pyglet much easier and more logical for me as well as a number of other users (especially beginners). I am working on a patch right now to add these features in to Pyglet 1.1. If anyone else has some suggestions about these issues or any other personal nitpicks, I would love to hear them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
