Changes

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.

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.

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 recognize that a student is ready for a new usage of a known feature. 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 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.

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.