5,705
edits
Changes
Jump to navigation
Jump to search
mLine 153:
Line 153: + + + + + + + + + + + + + + + + + + + +
Platform Team/Guide/Sweets Packaging (view source)
Revision as of 21:36, 3 September 2011
, 21:36, 3 September 2011no edit summary
* [http://0install.net/interface-spec.html Feed file format specification]
* [http://0install.net/interface-spec.html Feed file format specification]
* [http://0install.net/0compile.html 0compile] [http://0install.net/0compile-dev.html guide]
* [http://0install.net/0compile.html 0compile] [http://0install.net/0compile-dev.html guide]
== The workflow of regular Sugar doer will look like: ==
# Having a directory with Sugar project to develop.
#* Directory should be placed to one of default paths.
#* The only important element is a [[Platform Team/Sugar_Doers_Kit/Implementation#Recipes|recipe file]], i.e., an analog of {{Code|activity.info}} file for activities.
# To make it useful, just run it.
#* For activities, just click on activity icon in Sugar Shell.
#* Otherwise, run application using its unique Web url.
# Everything which is related to the process of project running, will be handled automatically.
#* There is always a way to fallback to the particular running step.
#* If project has dependencies, they will be installed or passed though the same running procedure (for under development dependencies).
#* If project needs to be build, it will happen automatically (including installing buildtime dependencies).
# Make Sugar project accessible for others.
#* Only one command call or one click in Sugar Shell is needed.
#* The only requirement, being registered in the system (particular implementations might be different, from [https://cas.sugarlabs.org/ Sugar Labs Central Login] to local school server).
#* Anyone can run recent version of your project just be mentioning its Web url.
# Sharing information about Sugar project.
#* Information about newly released project might be automatically published on [[Activity Library]].
-->
-->