Line 1: |
Line 1: |
| == Sugargame == | | == Sugargame == |
| | | |
− | Sugargame is a Python package which allows [http://www.pygame.org/ PyGame] | + | 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. |
Line 11: |
Line 11: |
| What it does: | | What it does: |
| | | |
− | * Wraps a Sugar activity around an existing PyGame program with few changes | + | * 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 | | * Allows Sugar toolbars and other widgets to be added to the activity UI |
| * Provides hooks for saving to and restoring from the Journal | | * Provides hooks for saving to and restoring from the Journal |
Line 19: |
Line 19: |
| See also [[Development Team/Sugargame/Examples]]. | | See also [[Development Team/Sugargame/Examples]]. |
| | | |
− | ==== 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 into it. For an example, see the directory named test, inside the Sugargame repository. It is in fact a Sugargame activity. | + | 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: |