OS Builder/Add additional Activities
Look into the sugar_activity_group and sugar_activities_extra modules.
sugar_activity_group
If your activities are published online and can being fetched from public URLs, and you can manage a "Sugar Activity Group page" the best option is to use sugar_activity_group. This works both for the builder and for later updates.
Define a 'base URL' -- for example, http://wiki.laptop.org/Activities/YourDeployment . Add the module to the modules list and a new section:
[sugar_activity_group] url=http://wiki.laptop.org/go/Activities/YourDeployment
The system will actually request a url adding the OS version number, so it will try, in order
http://wiki.laptop.org/go/Activities/YourDeployment/10.1.3 http://wiki.laptop.org/go/Activities/YourDeployment/10.1 http://wiki.laptop.org/go/Activities/YourDeployment/10 http://wiki.laptop.org/go/Activities/YourDeployment
For best control over activity versioning, create a page for this specific version http://wiki.laptop.org/go/Activities/YourDeployment/10.1.3 . The page uses theactivity microformat -- the easiest way is to start copying the contents of http://wiki.laptop.org/go/Activities/G1G1/10.1.3 or http://wiki.laptop.org/go/Activities/G1G1Lite/10.1.3
sugar_activities_extra
If your activities and content are not published, or you prefer to avoid maintaining a "Sugar Activity Group page", you can use sugar_activities_extra.
For just place them in a directory next to your INI file, and use the sugar_activities_extra module.
- Add sugar_activities_extra to the modules list
- For activities with a URL, just add a
[sugar_activities_extra] url_1=http://foo.com/MyActivity-1.xo url_2=http://foo.com/MyContent-3.xol
- For activities from your disk, create a directory
activities, and add instead
[sugar_activities_extra] local_dir=%(oob_config_dir)s/activities