Features/Smart Objects/Shared Actions

The purpose

• To have a Sugar tool that let students and teachers to be more concentrated on particular subject(s) during the class time
• Make this tool looks like a regular teaching workflow (in the class) as much as possible
• Keep this concentration for off-line mode, i.e., students' home work
• The cloud based approach but only on purpose, i.e., only for particular objects when clouds make sense and keep the rest student objects local and private. Thus:
  • protect teaching related objects from being removed by students to have more local space
  • easy access for teachers to all students' work
  • no need in special backup routines, everything is shared from the beginning and implicitly

Conception

1. object + tag + time = action, i.e., each action has duration
2. everything is on server
3. objects and actions might have tags
4. parental relationships for actions, action threads
5. the same objects might be used in several actions, objects have different states associated with different actions - object's history.
6. all (j)object are composite, they have different history for different users
7. action thread loops, useful for teachers since they teach the same from year to year and having a chance to compare what they do at this moment a year ago is useful