Changes

Jump to navigation Jump to search
no edit summary
Line 1: Line 1: −
<noinclude>{{ GoogleTrans-en}}
+
<noinclude>{{GoogleTrans-en}}
       
'''Please describe new feature requests by one of the methods below:'''
 
'''Please describe new feature requests by one of the methods below:'''
   −
'''Note:''' We periodically review these requests, generating ''enhancement tickets'' in [http://dev.sugarlabs.org our tracking system].
+
'''Note:''' We periodically review these requests, generating ''enhancement tickets'' in [http://trac.sugarlabs.org our tracking system].
* Developers: please continue to file feature requests directly in the [http://dev.sugarlabs.org tracking system] and develop proposals through the [[Features/Policy]] process.
+
* Developers: please continue to file feature requests directly in the [http://trac.sugarlabs.org tracking system] and develop proposals through the [[Features/Policy]] process.
 
* You may also use our new, '''[http://www.getsatisfaction.com/sugarlabs community-powered support site]''' to submit questions, ideas, problem reports, & praise.
 
* You may also use our new, '''[http://www.getsatisfaction.com/sugarlabs community-powered support site]''' to submit questions, ideas, problem reports, & praise.
 
* You may edit this and other pages of the wiki.  
 
* You may edit this and other pages of the wiki.  
Line 24: Line 24:  
It would be great if there was a Sugar OS auto-update tool in the Sugar interface (or a graphical control panel, as detailed below) to make keeping up-to-date easy.
 
It would be great if there was a Sugar OS auto-update tool in the Sugar interface (or a graphical control panel, as detailed below) to make keeping up-to-date easy.
   −
:This feature is being tracked in [http://dev.sugarlabs.org/ticket/105 Ticket #105].
+
:This feature is being tracked in [http://trac.sugarlabs.org/ticket/105 Ticket #105].
    
==Download Page==
 
==Download Page==
Line 58: Line 58:  
I have had some success, but there are many frustrations, the Journal interface being the most egregious.  Some notable troubles:
 
I have had some success, but there are many frustrations, the Journal interface being the most egregious.  Some notable troubles:
   −
* I spend an inordinate amount of time deleting Journal clutter.  It should be possible to turn automatic logging off, since not all activity will necessarily be worth tracking.  Better yet, include a GUI for setting filter options for what will be logged, and what will not be loggedov
+
* I spend an inordinate amount of time deleting Journal clutter.  It should be possible to turn automatic logging off, since not all activity will necessarily be worth tracking.  Better yet, include a GUI for setting filter options for what will be logged, and what will not be logged.
 
::We took [[Development_Team/Release/Releases/Sucrose/0.84#Resume_Activity|a different approach]] to the Journal spam issue.
 
::We took [[Development_Team/Release/Releases/Sucrose/0.84#Resume_Activity|a different approach]] to the Journal spam issue.
    
* The flat file display of directories on USB or SD devices also clutters the Journal.  Especially annoying is when a complete web page is saved on another computer and viewed on an XO (for example tutorial information about the XO).  The detail data in the subdirectory makes it hard to find the root HTML file to view the page.  Moreover, as nearly as I can tell, it is not possible to save a complete web page using only the XO.  Something is saved, but it displays incorrectly when viewed later.  This is of fundamental importance for areas with little or unreliable internet service.  A child finds something at school, he saves it so he can read it later at home where there is no internet, and what he gets is some partially readable glop.
 
* The flat file display of directories on USB or SD devices also clutters the Journal.  Especially annoying is when a complete web page is saved on another computer and viewed on an XO (for example tutorial information about the XO).  The detail data in the subdirectory makes it hard to find the root HTML file to view the page.  Moreover, as nearly as I can tell, it is not possible to save a complete web page using only the XO.  Something is saved, but it displays incorrectly when viewed later.  This is of fundamental importance for areas with little or unreliable internet service.  A child finds something at school, he saves it so he can read it later at home where there is no internet, and what he gets is some partially readable glop.
::This feature request is being tracked in [http://dev.sugarlabs.org/ticket/584 Ticket 584].
+
::This feature request is being tracked in [http://trac.sugarlabs.org/ticket/584 Ticket 584].
    
* The OLPC developers guide extols the Journal as a replacement for file hierarchies, and suggests that such hierarchies are unnatural.  This is not true:  containers are very intuitive, especially for children.  Even in the most primitive hut, there is an area for cooking, which contains a larder which contains food items.  The cooking area also contains a storage area for utensils and an area for food preparation.  The hut itself contains a sleeping area, a cooking area, a latrine area and a social area, even if it is only one room.  Moreover, the hut is contained in a community, itself contained in a nation.  To assert that hierarchical organization is unnatural borders on blind hubris.  Hierarchical organization of information is no exception: bearing witness are the containers library, collection, shelf, volume, and page within the volume.  Indeed, the entire internet, the new global library, is intrinsically and irretrievably hierarchical.  Depriving children of these fundamental organizational tools is tantamount to crippling them.
 
* The OLPC developers guide extols the Journal as a replacement for file hierarchies, and suggests that such hierarchies are unnatural.  This is not true:  containers are very intuitive, especially for children.  Even in the most primitive hut, there is an area for cooking, which contains a larder which contains food items.  The cooking area also contains a storage area for utensils and an area for food preparation.  The hut itself contains a sleeping area, a cooking area, a latrine area and a social area, even if it is only one room.  Moreover, the hut is contained in a community, itself contained in a nation.  To assert that hierarchical organization is unnatural borders on blind hubris.  Hierarchical organization of information is no exception: bearing witness are the containers library, collection, shelf, volume, and page within the volume.  Indeed, the entire internet, the new global library, is intrinsically and irretrievably hierarchical.  Depriving children of these fundamental organizational tools is tantamount to crippling them.
::Arguably this request is overstated–"crippling them"–but [http://dev.sugarlabs.org/ticket/584 Ticket 584] presumably will address this.
+
::Arguably this request is overstated–"crippling them"–but [http://trac.sugarlabs.org/ticket/584 Ticket 584] presumably will address this.
    
* With reference to the previous point, it would be nice to have something like the triangle by directories on Macs, or in the example listings in pippy: click on the triangle, and the contained information is toggled between hidden and expanded states.  A child could create a container in the Journal, and drag different Journal entries into it to organize the log of his activities according to his own choosing, and then click on the triangle to hide those that are distracting to the activity at hand.  This is conceptually no different than putting toys away in a toy box, and it ''is'' perfectly natural to all human beings, children or otherwise.  Moreover, this functionality is already present, but only for 'hard' containers like USB and SD devices.  Is it such a stretch to allow 'soft' user created containers as journal entries?
 
* With reference to the previous point, it would be nice to have something like the triangle by directories on Macs, or in the example listings in pippy: click on the triangle, and the contained information is toggled between hidden and expanded states.  A child could create a container in the Journal, and drag different Journal entries into it to organize the log of his activities according to his own choosing, and then click on the triangle to hide those that are distracting to the activity at hand.  This is conceptually no different than putting toys away in a toy box, and it ''is'' perfectly natural to all human beings, children or otherwise.  Moreover, this functionality is already present, but only for 'hard' containers like USB and SD devices.  Is it such a stretch to allow 'soft' user created containers as journal entries?
Line 71: Line 71:     
* I have discovered that a journal entry is really a saving of the state of an activity comprising data, activity, view state (not always restored properly), etc.  This notion of a saved state that may be identically resumed is very good, and very convenient, when it has been fully implemented by an activity.  It should extend to power cycles.  When I turn the machine back on, all my running activities should be resumed and the clipboard should have all my clips, and the machine view should be restored to the most recent active activity before power cycling.
 
* I have discovered that a journal entry is really a saving of the state of an activity comprising data, activity, view state (not always restored properly), etc.  This notion of a saved state that may be identically resumed is very good, and very convenient, when it has been fully implemented by an activity.  It should extend to power cycles.  When I turn the machine back on, all my running activities should be resumed and the clipboard should have all my clips, and the machine view should be restored to the most recent active activity before power cycling.
::This feature request is being tracked in [http://dev.sugarlabs.org/ticket/585 Ticket 585].
+
::This feature request is being tracked in [http://trac.sugarlabs.org/ticket/585 Ticket 585].
    
* With reference to the previous point, this distinction between what a journal entry really is and a file or directory (which are very useful containers, not at all obsolete) should be made clearer.  Downloads are implicitly files (documents or data if you prefer), not activities.  Often, there is no natural activity for working with a download, or the default activity may be cumbersome or unworkable.  The only workable means for accessing a download that I have discovered is to copy it to a USB or SD device, and then use the command line to manipulate it.  The rudimentary task of managing development files has required me to repeatedly resort to the command line, which I detest, being a primitive legacy of the days in the 1970's when 64kbyte mini-computers ruled.  It should be possible to copy, delete, rename, and execute files from the browser activity.  This is the 21st century after all.
 
* With reference to the previous point, this distinction between what a journal entry really is and a file or directory (which are very useful containers, not at all obsolete) should be made clearer.  Downloads are implicitly files (documents or data if you prefer), not activities.  Often, there is no natural activity for working with a download, or the default activity may be cumbersome or unworkable.  The only workable means for accessing a download that I have discovered is to copy it to a USB or SD device, and then use the command line to manipulate it.  The rudimentary task of managing development files has required me to repeatedly resort to the command line, which I detest, being a primitive legacy of the days in the 1970's when 64kbyte mini-computers ruled.  It should be possible to copy, delete, rename, and execute files from the browser activity.  This is the 21st century after all.
::This is being worked through in a slightly different way as discussed in [http://dev.sugarlabs.org/ticket/574 Ticket 574].
+
::This is being worked through in a slightly different way as discussed in [http://trac.sugarlabs.org/ticket/574 Ticket 574].
    
* The simple task of saving a module created with Pippy into a suitable library directory turns into an ordeal because of these limitations on necessary functionality which ultimately serves not to educate, but to handicap children.
 
* The simple task of saving a module created with Pippy into a suitable library directory turns into an ordeal because of these limitations on necessary functionality which ultimately serves not to educate, but to handicap children.
Line 133: Line 133:     
:But what if you wish to connect to one of several jabber servers because you belong to several communities/SIGs?  I can live with one-at-a-time, but it would be wonderful if I could pick from a list I've created.  Or at least a list of jabber servers I've previously connected to.  How about a syntax for "choice <n> from file <x>" and "show me choices in file <x>"? -- davewa
 
:But what if you wish to connect to one of several jabber servers because you belong to several communities/SIGs?  I can live with one-at-a-time, but it would be wonderful if I could pick from a list I've created.  Or at least a list of jabber servers I've previously connected to.  How about a syntax for "choice <n> from file <x>" and "show me choices in file <x>"? -- davewa
:This feature request is being tracked in [http://dev.sugarlabs.org/ticket/587 Ticket 587]
+
:This feature request is being tracked in [http://trac.sugarlabs.org/ticket/587 Ticket 587]
    
== Browse ==
 
== Browse ==
    
I cannot copy a link, I can't save a jpg, the Sugar OS changes the filename of a file which it does not recognise, the directory system is hidden, there is no predictive text when typing URL's or usernames, there's no tabbed browsing, there's no cookie, proxy or popup control.
 
I cannot copy a link, I can't save a jpg, the Sugar OS changes the filename of a file which it does not recognise, the directory system is hidden, there is no predictive text when typing URL's or usernames, there's no tabbed browsing, there's no cookie, proxy or popup control.
:Browse 100 support copying/downloading images and links. (Wait for the hover menu or use the right mouse button on the object you are interested in.) The other feature requests are being tracked in [http://dev.sugarlabs.org/ticket/591 Ticket 591].
+
:Browse 100 support copying/downloading images and links. (Wait for the hover menu or use the right mouse button on the object you are interested in.) The other feature requests are being tracked in [http://trac.sugarlabs.org/ticket/591 Ticket 591].
    
== Printer Support ==
 
== Printer Support ==

Navigation menu