10,509
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: − + + + − + − − ==XO== − − * Opening − * Position of antennae − * Rotate screen button − * Book reader mode, and page controls Line 113:
Line 108: + + + + + + + + + + + + +
no edit summary
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
No matter how well we do in making Sugar and the XO discoverable, there are necessarily some things that even a born lever-puller and button-clicker will not find, or will not understand. This is a list of such issues. We can consider whether some of these can be improved, but we know that there is a limit. So we have to alert teachers to these issues, and assist them to alert the children.
Some ideas are not easy to discover; the concept of guided discovery, where a mentor helps point a learner in a fruitful direction can accelerate the pace of learning. Some Sugar features are not easy to discover and while we are working to improve upon this, we provide some guides to discovery below.
No matter how well we do in making Sugar discoverable, there are necessarily some things that even a born lever-puller and button-clicker will not find, or will not understand. This page contains a list of such things. We can consider whether some of these can be improved, but we know that there is a limit. So we have to alert teachers to these issues, and assist them to alert the children.
Nothing is 100% discoverable or 100% undiscoverable. There are many features of Sugar and the XO that can be discovered, without their use cases being in any way obvious. The question, then, is how to provide discovery projects where we know that a particular usage is appropriate, and include a hint on the feature in the lesson plan. In other cases, the children understand immediately what a function is for, as soon as they know it exists. In those cases, you generally don't have to show them twice.
Nothing is 100% discoverable or 100% undiscoverable. There are many features of Sugar that can be discovered, without their use cases being in any way obvious. The question, then, is how to provide discovery projects where we know that a particular usage is appropriate, and include a hint on the feature in the lesson plan. In other cases, the children understand immediately what a function is for, as soon as they know it exists. In those cases, you generally don't have to show them twice.
We should probably create a subpage for each of these issues, or point to an existing Wiki page that has the information.
We should probably create a subpage for each of these issues, or point to an existing Wiki page that has the information.
==Sugar UI==
==Sugar UI==
We also need to be clear about skills that need practice more than discovery, as in music and sports, or keyboarding or language. What is the proper balance?
We also need to be clear about skills that need practice more than discovery, as in music and sports, or keyboarding or language. What is the proper balance?
==Hardware==
Sugar runs on hardware and there are some hardware specific interactions that can be difficult to discover. For example, the function keys (F1–F4) map to the Sugar zoom levels. These mapping are evident on the OLPC XO-1 hardware, which has dedicated symbols on those keys, but not as easy to discover on generic keyboards. Similarly, there is a key dedicated to the Frame on the OLPC XO-1 keyboard. The Frame is accessed through a keyboard shortcut on a generic keyboard (Alt-F).
Listed below are some of the undiscoverable features specific to hardware.
===OLPC XO-1===
* Opening
* Position of antennae
* Rotate screen button
* Book reader mode, and page controls