Features/Smart Objects: Difference between revisions
Appearance
< Features
Link to new page |
No edit summary |
||
| Line 1: | Line 1: | ||
== The problems teachers complain == | == The problems teachers complain about == | ||
* Students remove useful | * Students remove useful Journal objects to free the space for other purposes. | ||
* | * Lack of storage space on the XO to keep all the objects kids want | ||
* Having only current backup procedure (backup/restore entirely journal) is awkward. If you need to keep only particular objects, this workflow is too ineffective and force | * Having only the current backup procedure (backup/restore entirely journal) is awkward. If you need to keep only particular objects, this workflow is too ineffective and force users to calculate trade-offs between loosing some files in order to restore others. | ||
== Solutions == | == Solutions == | ||
| Line 14: | Line 14: | ||
===Pages=== | ===Pages=== | ||
* [[Features/Mokurai & alsroot | Mokurai & alsroot discussion]] | * [[Talk:Features/Smart Objects#Mokurai & alsroot discussion | Mokurai & alsroot discussion]] | ||
{{Special:PrefixIndex/{{PAGENAMEE}}/}} | {{Special:PrefixIndex/{{PAGENAMEE}}/}} | ||
Revision as of 14:24, 9 June 2011
The problems teachers complain about
- Students remove useful Journal objects to free the space for other purposes.
- Lack of storage space on the XO to keep all the objects kids want
- Having only the current backup procedure (backup/restore entirely journal) is awkward. If you need to keep only particular objects, this workflow is too ineffective and force users to calculate trade-offs between loosing some files in order to restore others.
Solutions
Please create your page under this one with describing:
- how your solution works from students pov
- how your solution works from teachers pov