OS Builder/Add additional Activities

From OLPC
< OS Builder
Revision as of 22:06, 2 October 2016 by Quozl (talk | contribs) (rework)
Jump to navigation Jump to search

You can add additional activities using the sugar_activity_group and sugar_activities_extra modules.

An Activity Group page is a list of activities and download URLs. The page must use the Sugar activity microformat. The page does not need to be on the OLPC Wiki; it can be on your own web server or school server.

The Software Update feature will check the Activity Group page for updated activities.

sugar_activity_group

If your activities are published online or can being fetched by the laptops, and you can manage a Activity Group page, then use sugar_activity_group. This works both for the builder and the Software Update feature, so you can deliver updates during a deployment.

Define a base URL -- for example,

 http://wiki.laptop.org/go/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 builder will request a URL by adding the operating system version number, so it will try, in order:

 http://wiki.laptop.org/go/Activities/YourDeployment/13.2.7
 http://wiki.laptop.org/go/Activities/YourDeployment/13.2
 http://wiki.laptop.org/go/Activities/YourDeployment/13
 http://wiki.laptop.org/go/Activities/YourDeployment

For best control over activity versions, create an Activity Group page with the full operating system version number, for example:

 http://wiki.laptop.org/go/Activities/YourDeployment/13.2.7

An easy way is to start by copying the contents of Activities/13.2.7.

Using your own Activity Group page will hide updates from the OLPC Activity Group, so be sure to keep your page up to date.

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.

However, this method does not support Sugar's Software Update feature, so you cannot update activities automatically during deployment.

For activities with a URL, add:

 [sugar_activities_extra]
 url_1=http://activities.example.edu/MyActivity-1.xo
 url_2=http://activities.example.edu/MyContent-3.xol

For activities from your disk, put them in a activities, and add:

 [sugar_activities_extra]
 local_dir=%(oob_config_dir)s/activities