Development Team/Sugargame: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
* 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 === | ==== 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. | 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. | ||
| Line 29: | Line 29: | ||
== Using Sugargame == | == Using Sugargame == | ||
=== Wrapping a Pygame program === | ==== Wrapping a Pygame program ==== | ||
To use Sugargame to Sugarize a Pygame program, set up an activity directory and copy the Sugargame package to it. | To use Sugargame to Sugarize a Pygame program, set up an activity directory and copy the Sugargame package to it. | ||
| Line 56: | Line 56: | ||
gtk.main_iteration() | gtk.main_iteration() | ||
=== Adding Pygame to | ==== Adding Pygame to a PyGTK activity ==== | ||
To add Pygame to an existing Sugar activity, create a PygameCanvas widget and call run_pygame on it. | To add Pygame to an existing Sugar activity, create a PygameCanvas widget and call run_pygame on it. | ||