Sugar-api-doc: Difference between revisions
| Line 18: | Line 18: | ||
In the sugar model, all files needed to run an activity (the python code, icons, etc.) should be located under one directory: |
In the sugar model, all files needed to run an activity (the python code, icons, etc.) should be located under one directory: |
||
Every activity in the Sugar environment is packaged into a self-contained „bundle“. The bundle contains all the resources and executable code (other than system-provided base libraries) which the activity needs to execute. Any resources or executable code that is not provided by the base system just be packaged within the bundle. |<ref>[http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook OLPC Austria - Activity Handbook for Sugar]</ref>. |
|||
= Notes = |
= Notes = |
||
Revision as of 17:47, 11 June 2008
How do I get additional help beyond this almanac?
- Looking to get started with the basics of sugar development? Check out Christoph Derndorfer's Activity Handbook.
Now, on to the actual almanac ...
Package: sugar.activity
Package: sugar.graphics
MISCELLANEOUS
The tasks below are random useful techniques that have come up as I write code and documentation for this reference. They have yet to be categorized, but will be as a sufficient set of related entries are written.
How do I get the file path for my activity bundle?
In the sugar model, all files needed to run an activity (the python code, icons, etc.) should be located under one directory:
Every activity in the Sugar environment is packaged into a self-contained „bundle“. The bundle contains all the resources and executable code (other than system-provided base libraries) which the activity needs to execute. Any resources or executable code that is not provided by the base system just be packaged within the bundle. |<ref>OLPC Austria - Activity Handbook for Sugar</ref>.
Notes
<references />