Features/Content support - Revision history

Godiard at 19:19, 5 November 2013

2013-11-05T19:19:32Z

← Older revision		Revision as of 15:19, 5 November 2013
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TOCright}}		<noinclude>{{GoogleTrans-en}}{{TOCright}}
	[[Category:~~Feature~~\|Content support]]		[[Category:FeatureLanded\|Content support]]
	~~[[Category:Feature Page Incomplete]]~~</noinclude>		</noinclude>

	== Summary ==		== Summary ==

DanielDrake at 14:57, 4 July 2013

2013-07-04T14:57:54Z

Show changes

FGrose at 05:33, 18 October 2009

2009-10-18T05:33:25Z

← Older revision		Revision as of 01:33, 18 October 2009
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>		<noinclude>{{GoogleTrans-en}}{{TOCright}}
			[[Category:Feature\|Content support]]
			[[Category:Feature Page Incomplete]]</noinclude>

	== Summary ==		== Summary ==
Line 22:		Line 24:
	** This means that the content may be installed before any of the Sugar profile or datastore exists		** This means that the content may be installed before any of the Sugar profile or datastore exists
	* Easy for the user to install more content		* Easy for the user to install more content
	** e.g. single click from USB disk view in Journal, or website in Browse activity		** e.g., single click from USB disk view in Journal, or website in Browse activity
	* Accessible through the home screen.		* Accessible through the home screen.
	** Content should become a first-class citizen in the Sugar shell, alongside Activities.		** Content should become a first-class citizen in the Sugar shell, alongside Activities.
Line 29:		Line 31:
	** It would be fine for the Journal event view to note that new content has been installed, but this should not be the primary way of accessing such content.		** It would be fine for the Journal event view to note that new content has been installed, but this should not be the primary way of accessing such content.
	* Precisely one copy stored on disk, except for when explicitly saved to Journal		* Precisely one copy stored on disk, except for when explicitly saved to Journal
	** It is not acceptable for a 2nd copy of the content (e.g. the originating content bundle) to be stored in the journal, even if it is compressed, unless the user has explicitly made this action (e.g. drag-and-drop .xol bundle from USB to Journal)		** It is not acceptable for a 2nd copy of the content (e.g., the originating content bundle) to be stored in the journal, even if it is compressed, unless the user has explicitly made this action (e.g., drag-and-drop .xol bundle from USB to Journal)
	* Full compatibility with existing .xol content bundles		* Full compatibility with existing .xol content bundles

Line 36:		Line 38:
	Supporting .xol bundles is a must. They are already widely created and deployed in the field. Here are some examples of the kinds of bundles that exist:		Supporting .xol bundles is a must. They are already widely created and deployed in the field. Here are some examples of the kinds of bundles that exist:
	* World maps		* World maps
	* Music (e.g. one album)		* Music (e.g., one album)
	* Grade 3 textbooks		* Grade 3 textbooks
	* Grade 5 textbooks		* Grade 5 textbooks
Line 113:		Line 115:
	== Comments and Discussion ==		== Comments and Discussion ==
	* See [[{{TALKPAGENAME}}\|discussion tab for this feature]]		* See [[{{TALKPAGENAME}}\|discussion tab for this feature]]

	~~[[Category:Feature]]~~
	~~[[Category:Feature Page Incomplete]]~~

DanielDrake: /* Accessing content from home screen */

2009-08-20T10:40:44Z

Accessing content from home screen

← Older revision		Revision as of 06:40, 20 August 2009
Line 76:		Line 76:
	* If any event causes the interface to leave the home screen (for example: starting an activity, or switching to the network view) then the dialog box is automatically closed.		* If any event causes the interface to leave the home screen (for example: starting an activity, or switching to the network view) then the dialog box is automatically closed.
	** This ensures that if you return to the home screen by pressing F3, it is guaranteed that you will see the familiar XO-man icon which allows you to shutdown your computer.		** This ensures that if you return to the home screen by pressing F3, it is guaranteed that you will see the familiar XO-man icon which allows you to shutdown your computer.
			* If the dialog is active and on-screen, pressing F3 will cause the dialog to close.
			** This again ensures that pressing the "Home" key at any time will return you to the all-familiar favorites view including XO-man.
	* There would be room for changing/refining the design of this dialog in future, but hopefully the base idea would stay the same: it's an overlay over the home view, allowing you to select which things you want for easy access on the home view, and also allowing you to browse things by category.		* There would be room for changing/refining the design of this dialog in future, but hopefully the base idea would stay the same: it's an overlay over the home view, allowing you to select which things you want for easy access on the home view, and also allowing you to browse things by category.
	** Therefore we won't be shifting around design elements too much.		** Therefore we won't be shifting around design elements too much.

DanielDrake: /* Current status */

2009-08-18T17:07:13Z

Current status

← Older revision		Revision as of 13:07, 18 August 2009
Line 8:		Line 8:

	== Current status ==		== Current status ==
			Looking for people to spearhead the design and implementation of this feature.

	* Targeted release: (SUGAR_VERSION)		* Targeted release: (SUGAR_VERSION)
	* Last updated: (DATE)		* Last updated: (DATE)

DanielDrake at 17:04, 18 August 2009

2009-08-18T17:04:03Z

← Older revision		Revision as of 13:04, 18 August 2009
Line 111:		Line 111:

	[[Category:Feature]]		[[Category:Feature]]
			[[Category:Feature Page Incomplete]]

DanielDrake: /* Accessing content from home screen */

2009-08-18T17:00:14Z

Accessing content from home screen

← Older revision		Revision as of 13:00, 18 August 2009
Line 65:		Line 65:
	My ideas for the dialog design:		My ideas for the dialog design:
	* The dialog sits on top of the favorites view view, not full screen, styled like the control panel. Therefore it is obviously just another layer on the home view and doesn't present the confusing illusion that you're in the journal.		* The dialog sits on top of the favorites view view, not full screen, styled like the control panel. Therefore it is obviously just another layer on the home view and doesn't present the confusing illusion that you're in the journal.
	* There would be a bar along the top, like the control panel. From left to right, it would have~~: the XO figure from the favorites view (mouse-over or click with either button to open the palette giving options like Shutdown and Control Panel),~~ a search box, and an X to close the dialog.		* There would be a bar along the top, like the control panel. From left to right, it would have a search box and an X to close the dialog.
	* Directly below, there would be another bar with tab-like buttons for the following categories: Activities, Books, Health, Images, Media, Science, Search		* Directly below, there would be another bar with tab-like buttons for the following categories: Activities, Books, Health, Images, Media, Science, Search
	** Actual activities (write, paint, record) would be listed under the Activities category		** Actual activities (write, paint, record) would be listed under the Activities category
Line 72:		Line 72:
	** (side-project: It may make sense for activities themselves to allow themselves to be categorized this way too. e.g. TamTam would go under Media, Wikipedia under books, Maze under Games, etc.)		** (side-project: It may make sense for activities themselves to allow themselves to be categorized this way too. e.g. TamTam would go under Media, Wikipedia under books, Maze under Games, etc.)
	* The remainder of the dialog would be a list view, of identical appearance and behaviour to the current List View on the home screen (star, name, version, last accessed time)		* The remainder of the dialog would be a list view, of identical appearance and behaviour to the current List View on the home screen (star, name, version, last accessed time)
			* If any event causes the interface to leave the home screen (for example: starting an activity, or switching to the network view) then the dialog box is automatically closed.
			** This ensures that if you return to the home screen by pressing F3, it is guaranteed that you will see the familiar XO-man icon which allows you to shutdown your computer.
	* There would be room for changing/refining the design of this dialog in future, but hopefully the base idea would stay the same: it's an overlay over the home view, allowing you to select which things you want for easy access on the home view, and also allowing you to browse things by category.		* There would be room for changing/refining the design of this dialog in future, but hopefully the base idea would stay the same: it's an overlay over the home view, allowing you to select which things you want for easy access on the home view, and also allowing you to browse things by category.
	** Therefore we won't be shifting around design elements too much.		** Therefore we won't be shifting around design elements too much.

DanielDrake at 10:13, 18 August 2009

2009-08-18T10:13:31Z

Show changes

DanielDrake: Created page with '{{GoogleTrans-en}}{{TOCright}} == Summary == ''A sentence or two summarizing what this feature is and what it will do. This information is used for the ov…'

2009-08-18T06:16:00Z

Created page with '<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> == Summary == ''A sentence or two summarizing what this feature is and what it will do. This information is used for the ov…'

New page

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>

== Summary ==
''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''

== Owner ==
[[User:DanielDrake|DanielDrake]] dsd@laptop.org

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==

It could be useful to provide as simple as possible method for non-tech users e.g. sugar could send info to predefined server instead of asking questions.

== Benefit to Sugar ==

Easy way which lets user provide full debug info after encountering a bug.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

== How To Test ==
''This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.''

''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.''

''A good "how to test" should answer these four questions:''

* ''What special hardware / data / etc. is needed (if any)?
* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?
* ''What specific actions do I perform to check that the feature is working like it's supposed to?
* ''What are the expected results of those actions?''

== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''

== Dependencies ==
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like python?''

== Contingency Plan ==
''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] 

[[Category:Feature Page Incomplete]]
[[Category:Feature]]
----
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''