Platform Team/Guide/Sweets Packaging: Difference between revisions
RafaelOrtiz (talk | contribs) m typo |
|||
| Line 215: | Line 215: | ||
and see its {{Code|sweets.recipe}} files. | and see its {{Code|sweets.recipe}} files. | ||
=== | == 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: | ||
| Line 239: | Line 243: | ||
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 == | ||