On Sat, Apr 17, 2010 at 12:19 AM, Joe Wreschnig <[email protected]> wrote: > I've made a clone repository for some work I am going to do on pyglet > sprites at http://code.google.com/r/joewreschnig-sprites/. Some of the > changes I'm going to make I don't expect to ever be merged back (use > radians instead of degrees for rotation) but others I would like to > see in mainline pyglet (the one commit I've made so far is a major > optimization to VertexBufferObjectRegion.invalidate). Should I send > requests to this list periodically asking for people to pull my > changes back into the mainline branches, or should I ask for mainline > commit rights and do it myself - fair warning, I'll probably screw > something up since I don't know Mercurial that well.
I've created issues #480, #481, and #482 for what I think are the most important changes in my repository so far, as the consensus seems to be that we should be using the pyglet issue tracker at least for now. This is an optimization for VertexBufferObjectRegion.invalidate. I'm not sure what to say about it. It's trivial and much faster. http://code.google.com/p/pyglet/issues/detail?id=480 This adds independent x and y scaling to sprites. There are two bugs in the first patch which are fixed in the second and third. http://code.google.com/p/pyglet/issues/detail?id=481 This adds a property to get/set X, Y, and rotation at the same time; the rationale is the same as the position property, to reduce vertex buffer updates. http://code.google.com/p/pyglet/issues/detail?id=482 -- 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.
