Changes

m
no edit summary
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]]