Features/Optional activity updates - Revision history

Godiard at 19:40, 20 April 2015

2015-04-20T19:40:18Z

← Older revision		Revision as of 15:40, 20 April 2015
Line 1:		Line 1:
	<noinclude>		<noinclude>
	[[Category:~~Feature~~\|Optional activity updates]]		[[Category:FeatureLanded\|Optional activity updates]]
	~~[[Category:Feature Page Incomplete~~]]
	</noinclude>		</noinclude>

Tch: /* Scope and implementation */

2014-08-06T13:36:57Z

Scope and implementation

← Older revision		Revision as of 09:36, 6 August 2014
Line 40:		Line 40:
	* 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 ~~entried~~ that need to be marked as optional.		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 ==

FGrose at 00:42, 6 August 2014

2014-08-06T00:42:02Z

← Older revision		Revision as of 20:42, 5 August 2014
Line 1:		Line 1:
	<noinclude>		<noinclude>
			[[Category:Feature\|Optional activity updates]]
	[[Category:Feature Page Incomplete]]		[[Category:Feature Page Incomplete]]
	~~[[Category:FeatureLanded\|Optional activity updates]]~~
	</noinclude>		</noinclude>

Tch: /* Scope and implementation */

2014-08-06T00:17:55Z

Scope and implementation

← Older revision		Revision as of 20:17, 5 August 2014
Line 40:		Line 40:
	* 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 ~~when needed~~.		This implementation is backwards compatible. Deployment that don't need to use this feature can simply ignore it. This field is used only entried that need to be marked as optional.

	== How to test ==		== How to test ==

Tch: /* User Experience */

2014-08-06T00:15:11Z

User Experience

← Older revision		Revision as of 20:15, 5 August 2014
Line 58:		Line 58:

	== User Experience ==		== User Experience ==
	User experienced is untouched~~, this feature is backwards compatible~~.		User experienced is untouched.

Tch: /* How to test */

2014-08-06T00:14:49Z

How to test

← Older revision		Revision as of 20:14, 5 August 2014
Line 44:		Line 44:
	== How to test ==		== How to test ==

	Modify your microformat file (ie., wiki or [https://github.com/tchx84/bundletools bundletools]) and ~~modify~~ activities entries ~~that needs to be mark as optional~~ 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>

Tch: /* How to test */

2014-08-06T00:13:41Z

How to test

← Older revision		Revision as of 20:13, 5 August 2014
Line 44:		Line 44:
	== 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 modify activities entries that needs to be mark as optional as follows:

	<pre>		<pre>

Tch: /* Scope and implementation */

2014-08-06T00:12:10Z

Scope and implementation

← Older revision		Revision as of 20:12, 5 August 2014
Line 33:		Line 33:
	== 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.
Line 40:		Line 40:
	* 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 ~~(no need to mark activities if not~~ needed).		This implementation is backwards compatible. Deployment that don't need to use this feature can simply ignore it. This field is used only when needed.

	== How to test ==		== How to test ==

Tch: /* Scope and implementation */

2014-08-06T00:10:02Z

Scope and implementation

← Older revision		Revision as of 20:10, 5 August 2014
Line 39:		Line 39:
	* 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 (no need to mark activities if not needed).

	== How to test ==		== How to test ==

Tch: /* Detailed Description */

2014-08-06T00:08:46Z

Detailed Description

← Older revision		Revision as of 20:08, 5 August 2014
Line 20:		Line 20:
	''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.