Development Team/Sugargame: Difference between revisions
No edit summary |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Sugargame == | == Sugargame == | ||
Sugargame is a Python package which allows [http://www.pygame.org/ | Sugargame is a Python package which allows [http://www.pygame.org/ Pygame] | ||
programs to run well under Sugar. | programs to run well under Sugar. | ||
It is a fork of olcpgames, which is no longer maintained. | It is a fork of olcpgames, which is no longer maintained. | ||
What it does: | |||
* Wraps a Sugar activity around an existing Pygame program with few changes | |||
* Allows Sugar toolbars and other widgets to be added to the activity UI | |||
* Provides hooks for saving to and restoring from the Journal | |||
Get it from: | Get it from: | ||
http:// | http://github.com/sugarlabs/sugargame | ||
And place it within your activity source. It is not part of Sugar. Remember to check back for updates when you are continuing development of your activity. | |||
You can find it in some activities already. It is so small that the duplication is unimportant. | |||
== Using Sugargame == | == Using Sugargame == | ||
| Line 21: | Line 25: | ||
==== 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 use Sugargame to Sugarize a Pygame program, set up an activity directory and copy the Sugargame package into it. For an example, see the directory named test, inside the Sugargame repository. It is in fact a Sugargame activity. | ||
The activity directory should look something like this: | The activity directory should look something like this: | ||