XS Community Edition/0.4/Services/Content update: Difference between revisions
< XS Community Edition | 0.4
Jump to navigation
Jump to search
m (moved User:Holt/XS Community Edition/0.4/Services/Content update to XS Community Edition/0.4/Services/Content update) |
|||
(4 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{xsce}} |
|||
You've got your .xo files, set up your activities.info file, it's all on a USB drive in a dir named xs-activity-server, and now that you've got all the ingredients, the last order of business is to create a manifest for the XSCE to read. |
You've got your .xo files, set up your activities.info file, it's all on a USB drive in a dir named xs-activity-server, and now that you've got all the ingredients, the last order of business is to create a manifest for the XSCE to read. |
||
Line 15: | Line 16: | ||
<ol> |
<ol> |
||
<li>Get the bundle_id for the Activity by running: |
<li>Get the bundle_id for the Activity by running:<br> |
||
<code>zipgrep bundle_id activityname.xo</code> |
<code>zipgrep bundle_id activityname.xo</code> |
||
<br> |
|||
That command will return something like: |
That command will return something like:<br> |
||
<code>JAMediaTube.activity/activity/activity.info:bundle_id = org.laptop.JAMediaTube</code> |
<code>JAMediaTube.activity/activity/activity.info:bundle_id = org.laptop.JAMediaTube</code> |
||
<br> |
|||
The bundle_id is the section after the = sign. |
The bundle_id is the section after the = sign. |
||
Line 29: | Line 28: | ||
<li>Create a section for each activity in the activities.info file which contains: |
<li>Create a section for each activity in the activities.info file which contains: |
||
<code>[bundle_id] |
<code>[bundle_id]<br> |
||
description = text description</code> |
description = text description</code><br> |
||
<br> |
|||
For example: |
For example:<br> |
||
<br> |
|||
<code>[org.laptop.JAMediaTube] |
<code>[org.laptop.JAMediaTube]<br> |
||
description = Watch YouTube! It's really fun! |
description = Watch YouTube! It's really fun!<br> |
||
<br> |
|||
[org.laptop.FakeActivity] |
[org.laptop.FakeActivity]<br> |
||
description = This is a placeholder for documentation purposes</code> |
description = This is a placeholder for documentation purposes</code> |
||
</ol> |
</ol> |
Latest revision as of 23:49, 8 August 2013
This IIAB XSCE content does not reflect the opinion of OLPC. These pages were created by members of a volunteer community supporting OLPC and deployments.
You've got your .xo files, set up your activities.info file, it's all on a USB drive in a dir named xs-activity-server, and now that you've got all the ingredients, the last order of business is to create a manifest for the XSCE to read.
Creating the activity updater
Copying activities
- Insert your USB drive into your computer (I used my regular FAT32 formatted drive that I also use for flashing XOs)
- Create a directory named xs-activity-server
- Navigate into the xs-activity-server dir.
- Download some activities.
Create Activity Descriptions
Activity Descriptions are shown in http://schoolserver/activities
- Get the bundle_id for the Activity by running:
zipgrep bundle_id activityname.xo
That command will return something like:
JAMediaTube.activity/activity/activity.info:bundle_id = org.laptop.JAMediaTube
The bundle_id is the section after the = sign. - Create file named activities.info in the xs-activity-server dir.
- Create a section for each activity in the activities.info file which contains:
[bundle_id]
description = text description
For example:
[org.laptop.JAMediaTube]
description = Watch YouTube! It's really fun!
[org.laptop.FakeActivity]
description = This is a placeholder for documentation purposes
Create manifest
- Run this command:
sha1sum *.xo *.info > manifest.sha1
- Eject the USB drive and plug it into the XSCE.
Update a School Server
The activities you put on the USB drive in the xs-activity-server dir will be installed. they will appear at http://schoolserver/activities.
- Plug the USB drive into the XSCE.
- Remove the USB drive
I don't know how the USB drive gets ejected by novice users from the XSCE. Which could be a concern?