As part of my GSoC project , I've been researching Pygame's sprite.py and
equivalents in other libraries, figuring out a list of features I will focus on
in my project.
I wanted to get your thoughts and feedback on these items; which of these do
you think are necessary, and which more necessary than the others? Do you think
implementing any of these would be too difficult for a first-time contributor
(me)? Do you have any other ideas?
Suggested improvements for sprite.py:
1. Easier positioning methods: Using tuples or arrays, instead of just Rects.
2. Setting a sprite's anchor points for handling in movement, animation,
3. Aggregated sprite class (basically, a sprites group which implements the
4. Automated dirty rendering (existing feature in Spyral ).
5. New visual attributes for sprites:
- Rotation angle
- Crop rectangle
- Collision parameters (smaller hitbox, etc.)
6. Alternative forms of collision detecting (not limited to circles and
Possibly using algorithms such as quadtrees and spatial hashing.
7. Improved layering system.
8. Respecting blendmode flags are handled in all types of sprites.
9. Animated sprites:
- Setting a group of images to cycle through in a time interval.
- Animating visual attributes, a-la Kivy  or CSS transitions .
10. Events dispatching from groups to sprites.
This list was comprised after consulting with mentor Robert Deaton (masquerade)
and fellow contributors on the IRC channel.
It's obviously not a final list of the work I'm planning, but more of a list of
things to research before I get to coding.
I would love to hear your feedback on these.
 Pygame SoC application: Improved Sprite and Scene system
 Spyral http://www.eecis.udel.edu/~rdeaton/spyral/
 Animation in Kivy http://kivy.org/docs/api-kivy.animation.html
 CSS Transitions https://developer.mozilla.org/en/CSS/CSS_transitions
Your friend in time,
sa...@maoz.info // +1 (347) 556.5044 // +972 (52) 834-3339
/* simba says roar! */