628
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − [[Category:Feature Page Incomplete]] Line 20:
Line 19: − + − + Line 33:
Line 32: − + Line 39:
Line 38: + + − + Line 56:
Line 57: − +
Features/Optional activity updates (view source)
Revision as of 15:40, 20 April 2015
, 15:40, 20 April 2015no edit summary
<noinclude>
<noinclude>
[[Category:FeatureLanded|Optional activity updates]]
[[Category:FeatureLanded|Optional activity updates]]
</noinclude>
</noinclude>
''This proposal is based around the needs of the OLPC project in Australia, but reflects a common need (current or future) of other OLPC implementations as well.''
''This proposal is based around the needs of the OLPC project in Australia, but reflects a common need (current or future) of other OLPC implementations as well.''
'''The problem:''' Previously, Daniel Drake implemented a mechanism for automatic activities updates. This was of great help for OLPC deployments such as Australia. However, the current mechanism will update (or install) ALL the activities in the updates list. This becomes a problem when not all the activities are intended for automatic updates, ie., when the bundle size is too big for massive automatic installation.
'''The problem:''' Previously, Daniel Drake implemented a mechanism for automatic activities updates. This was of great help for OLPC deployments such as Australia. However, the current mechanism will update (or install) ALL the activities in the updates list. This becomes a problem when not all the activities are intended for automatic updates, ie., when the bundle size is too big for massive automatic installation. In the practice deployments do not enable automatic updates because this kind of concerns.
The proposed solution is to provide a way to mark activities in the microformat file as "optional". Activities marked as optional will:
The proposed solution is to provide a way to mark activities in the microformat file as optional. Activities marked as optional will:
* Not be updated or installed during automatic updates.
* Not be updated or installed during automatic updates.
== Scope and implementation ==
== Scope and implementation ==
A initial implementation can be found in [https://github.com/tchx84/sugar/commits/optional-updates|here]
A initial implementation can be found in [https://github.com/tchx84/sugar/commits/optional-updates here]. The changes are:
* extend microformat parser to extract a new olpc-activity-optional field.
* extend microformat parser to extract a new olpc-activity-optional field.
* filter activities that are marked as optional when running in automatic mode.
* filter activities that are marked as optional when running in automatic mode.
* do not select activities marked as optional in the updater UI list.
* do not select activities marked as optional in the updater UI list.
This implementation is backwards compatible. Deployment that don't need to use this feature can simply ignore it. This field is used only on entries that need to be marked as optional.
== How to test ==
== How to test ==
Modify your microformat file (in the server, ie., wiki or via [https://github.com/tchx84/bundletools|bundletools]) and modify activities entry as follows:
Modify your microformat file (ie., wiki or [https://github.com/tchx84/bundletools bundletools]) and only mark optional activities entries as follows:
<pre>
<pre>
== User Experience ==
== User Experience ==
User experienced is untouched, this feature is backwards compatible.
User experienced is untouched.