Features/Sugar Bundles - Revision history

Alsroot at 12:02, 23 August 2010

2010-08-23T12:02:30Z

← Older revision		Revision as of 08:02, 23 August 2010
Line 1:		Line 1:
	<noinclude>{{TOCright}}		<noinclude>{{TOCright}}
	~~[[Category:Feature Ready for Release Manager]]~~
	[[Category:Feature\|Sugar Bundles]]		[[Category:Feature\|Sugar Bundles]]
	<!-- You can add categories to tie features back to real deployments/schools requesting them, for example		<!-- You can add categories to tie features back to real deployments/schools requesting them, for example

2009-12-28T17:31:58Z

Documentation

← Older revision		Revision as of 13:31, 28 December 2009
Line 118:		Line 118:
	* [http://wiki.laptop.org/go/Manifest_Specification#Contents_Manifests MANIFEST specification]		* [http://wiki.laptop.org/go/Manifest_Specification#Contents_Manifests MANIFEST specification]
	* Email threads		* Email threads
			** [http://thread.gmane.org/gmane.linux.laptop.olpc.sugar/19495/focus=19499 Sugar Bundles request for inclusion to 0.88]
	** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg10708.html Activity as a regular Journal Object request for inclusion to 0.88]		** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg10708.html Activity as a regular Journal Object request for inclusion to 0.88]
	** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06874.html Object Bundles review and inclusion to 0.86/Feature_List request Object Bundles]		** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06874.html Object Bundles review and inclusion to 0.86/Feature_List request Object Bundles]

2009-11-30T18:54:54Z

Documentation

← Older revision		Revision as of 14:54, 30 November 2009
Line 118:		Line 118:
	* [http://wiki.laptop.org/go/Manifest_Specification#Contents_Manifests MANIFEST specification]		* [http://wiki.laptop.org/go/Manifest_Specification#Contents_Manifests MANIFEST specification]
	* Email threads		* Email threads
			** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg10708.html Activity as a regular Journal Object request for inclusion to 0.88]
	** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06874.html Object Bundles review and inclusion to 0.86/Feature_List request Object Bundles]		** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06874.html Object Bundles review and inclusion to 0.86/Feature_List request Object Bundles]
	** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg07572.html multiple activity versions installed simultaneously]		** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg07572.html multiple activity versions installed simultaneously]

2009-11-29T19:36:36Z

adjusted category sort alias

← Older revision		Revision as of 15:36, 29 November 2009
Line 1:		Line 1:
	<noinclude>{{TOCright}}		<noinclude>{{TOCright}}
	[[Category:Feature Ready for Release Manager]]		[[Category:Feature Ready for Release Manager]]
	[[Category:Feature\|~~<Feature Name>~~]]		[[Category:Feature\|Sugar Bundles]]
	<!-- You can add categories to tie features back to real deployments/schools requesting them, for example		<!-- You can add categories to tie features back to real deployments/schools requesting them, for example
	[[Category:Features requested by School Xyz\|<Feature Name>]] (the \|Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->		[[Category:Features requested by School Xyz\|<Feature Name>]] (the \|Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->

2009-11-27T19:41:12Z

Scope

← Older revision		Revision as of 15:41, 27 November 2009
Line 89:		Line 89:
	* sugar		* sugar
	* sugar-toolkit		* sugar-toolkit

			== UI Design ==

			Nothing except related [[Features/Activity as a regular Journal Object]] feature.

	== How To Test ==		== How To Test ==

2009-11-27T18:39:31Z

Specification

← Older revision		Revision as of 14:39, 27 November 2009
Line 55:		Line 55:
	\|-		\|-
	\| ''entry''		\| ''entry''
	\| optional(depends on content)		\| optional<br>(depends on content)
	\| defines access point within the bundle(e.g. index.html for library bundles)		\| defines access point within the bundle(e.g. index.html for library bundles)
	\|-		\|-

2009-11-27T18:39:18Z

Specification

← Older revision		Revision as of 14:39, 27 November 2009
Line 55:		Line 55:
	\|-		\|-
	\| ''entry''		\| ''entry''
	\| ~~mandatory~~		\| optional(depends on content)
	\| defines access point to within bundle (e.g. index.html for library bundles)		\| defines access point within the bundle(e.g. index.html for library bundles)
	\|-		\|-
	\| ''mime_type''		\| ''mime_type''

2009-11-27T18:37:27Z

Specification

← Older revision		Revision as of 14:37, 27 November 2009
Line 46:		Line 46:
	Sugar bundle should have METADATA file in the top directory(or in <some_name>/ directory) of .xo bundle. This file is in [http://docs.python.org/library/configparser.html INI] format which describes how to setup bundle.		Sugar bundle should have METADATA file in the top directory(or in <some_name>/ directory) of .xo bundle. This file is in [http://docs.python.org/library/configparser.html INI] format which describes how to setup bundle.

	METADATA file can have one or several sections(depends on content) that describe metadata fields of final entry(ies) in Journal.		METADATA file can have one or several sections(depends on content) that describe metadata fields of final entry(ies) in Journal and other data that could be useful for sugar(depends on content).

	{\| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"		{\| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"

2009-11-27T18:36:32Z

Specification

← Older revision		Revision as of 14:36, 27 November 2009
Line 46:		Line 46:
	Sugar bundle should have METADATA file in the top directory(or in <some_name>/ directory) of .xo bundle. This file is in [http://docs.python.org/library/configparser.html INI] format which describes how to setup bundle.		Sugar bundle should have METADATA file in the top directory(or in <some_name>/ directory) of .xo bundle. This file is in [http://docs.python.org/library/configparser.html INI] format which describes how to setup bundle.

	METADATA file can have one or several sections(depends on ~~installation method~~) that describe metadata fields of final entry(ies) in Journal.		METADATA file can have one or several sections(depends on content) that describe metadata fields of final entry(ies) in Journal.

	{\| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"		{\| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"

2009-11-27T18:33:07Z

Specification

← Older revision		Revision as of 14:33, 27 November 2009
Line 68:		Line 68:
	\| optional		\| optional
	\| any [[Features/Plain_Query_Format#System_terms\|system]], [[Features/Plain_Query_Format#Users_predefined_terms\|users predefined]] and arbitrary Datastore field		\| any [[Features/Plain_Query_Format#System_terms\|system]], [[Features/Plain_Query_Format#Users_predefined_terms\|users predefined]] and arbitrary Datastore field
			\|-
			\| ''*''
			\| optional
			\| any tag, depends on content(inherited from activity bundles etc.)
	\|-		\|-
	\|}		\|}