5,705
edits
Changes
Platform Team/Guide/Sweets Packaging (view source)
Revision as of 18:54, 6 December 2011
, 18:54, 6 December 2011→Developing activities
and see its {{Code|sweets.recipe}} files.
and see its {{Code|sweets.recipe}} files.
=== Developing activities ===
== Developing activities ==
How Sweets might be useful while developing activities.
=== Manage sources ===
The traditional development related routine for activity sources is to run the {{Code|setup.py}} script located in the root activity directory. With Sweets, these routines might be accomplished with the {{Code|sweets}} command. Here is some background information:
The traditional development related routine for activity sources is to run the {{Code|setup.py}} script located in the root activity directory. With Sweets, these routines might be accomplished with the {{Code|sweets}} command. Here is some background information:
sweets build [PATH]
sweets build [PATH]
=== Launch activity ===
Before starting Sugar Shell, place your activity's sources directory to {{Code|~/Activities}}, or place there a symbolic link to activity sources. After running Sugar Shell, new activity will appear in Home (if it's absent in Favorites View, switch to List View).
== Good practices ==
== Good practices ==