Development Team/Sugargame: Difference between revisions
Created page with '== Sugargame == Sugargame is a Python package which allows [http://www.pygame.org/ Pygame] programs to run well under Sugar. It is fork of the olcpgames framework, which is no …' |
|||
| Line 13: | Line 13: | ||
* Provides hooks for saving to and restoring from the Journal | * Provides hooks for saving to and restoring from the Journal | ||
=== Differences between Sugargame and olpcgames === | |||
The olpcgames framework provides a wrapper around Pygame which attempts to allow a Pygame program to run mostly unmodified under Sugar. To this end, the Pygame program is run in a separate thread with its own Pygame message loop while the main thread runs the GTK message loop. Also, olpcgames wraps Sugar APIs such as the journal and mesh into a Pygame-like API. | |||
Sugargame takes a simpler approach; it simply offers a way to embed Pygame into a GTK widget. The Sugar APIs are used to interact with Sugar, the Pygame APIs are used for the game. | |||
Sugargame advantages: | |||
* Simpler code | * Simpler code | ||
* More elegant interface between Pygame and GTK | * More elegant interface between Pygame and GTK | ||
* Runs as a single thread: no thread related segfaults | * Runs as a single thread: no thread related segfaults | ||
* Possible to use Sugar widgets with Pygame | |||
Sugargame limitations: | |||
* No support for Pango or SVG sprites (yet) | |||
== Using Sugargame == | == Using Sugargame == | ||