Sugar-api-doc: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 12: | Line 12: | ||
= MISCELLANEOUS = |
= 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 body of related code is written. |
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 body of related code is 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 <ref>[http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook OLPC Austria - Activity Handbook for Sugar</ref>. |
Revision as of 17:34, 11 June 2008
The links below lead to moredetailed documentation of each package/class.
- Looking to get started with the basics of sugar development? Check out Christoph Derndorfer's Activity Handbook.
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 body of related code is 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 <ref>[http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook OLPC Austria - Activity Handbook for Sugar</ref>.