Difference between revisions of "Features/Smart Objects/Shared Actions"
< Features | Smart Objects
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
** no need in special backup routines, everything is shared from the beginning and implicitly | ** no need in special backup routines, everything is shared from the beginning and implicitly | ||
| − | {{Show|Conception| | + | {{Show|Conception |<pre> |
| − | + | - object + tag + time = action, i.e., each action has duration | |
| − | + | - everything is on server | |
| − | + | - objects and actions might have tags | |
| − | + | - parental relationships for actions, action threads | |
| − | + | - the same objects might be used in several actions, | |
| − | + | objects have different states associated with different | |
| − | + | actions - object's history. | |
| − | + | - all (j)object are composite, they have different history | |
| − | + | for different users | |
| + | - 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 | ||
| + | - two views for the same action, one for students (viewer/actor) | ||
| + | and one for teachers (initiator/moderator) | ||
| + | </pre> | ||
}} | }} | ||
| Line 30: | Line 36: | ||
# client "New action" to start action "New topic" | # client "New action" to start action "New topic" | ||
# new action will be automatically inherit objects: | # new action will be automatically inherit objects: | ||
| − | # * teacher himself | + | #* teacher himself |
| − | # * students | + | #* students |
# will indirectly inherit tags from inherited objects: | # will indirectly inherit tags from inherited objects: | ||
| − | # * the subject of the lesson, from teacher | + | #* the subject of the lesson, from teacher |
| − | # * the class number from students | + | #* the class number from students |
# UI will help with inheriting: | # UI will help with inheriting: | ||
| − | # * action tags | + | #* action tags |
| − | # * activities | + | #* activities |
| − | # * journal objects | + | #* journal objects |
# teacher sets new action tag "Next Topic" according to the teaching plan and adds: | # teacher sets new action tag "Next Topic" according to the teaching plan and adds: | ||
| − | # * new activities for that topic | + | #* new activities for that topic |
| − | # * journal objects to show students new topic on examples | + | #* journal objects to show students new topic on examples |
# teacher creates last action the lesson - "Home work" and | # teacher creates last action the lesson - "Home work" and | ||
# inherit activities form the 2nd one | # inherit activities form the 2nd one | ||
Revision as of 18:12, 2 June 2011
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
- object + tag + time = action, i.e., each action has duration - everything is on server - objects and actions might have tags - parental relationships for actions, action threads - the same objects might be used in several actions, objects have different states associated with different actions - object's history. - all (j)object are composite, they have different history for different users - 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 - two views for the same action, one for students (viewer/actor) and one for teachers (initiator/moderator)
Teacher workflow
Teacher creates a plan for future lesson in actions builder UI
- in actions browse, find an action for the last lesson (of the class teacher is planing new lesson) among already happened actions/lessons that are stored on the server
- click "Next Lesson" button to start planing new lesson
- the builder will add already existed (but not yet finished) "Home work" action attached to previous lesson actions, that action will be used to check how students' home work in the class
- client "New action" to start action "New topic"
- new action will be automatically inherit objects:
- teacher himself
- students
- will indirectly inherit tags from inherited objects:
- the subject of the lesson, from teacher
- the class number from students
- UI will help with inheriting:
- action tags
- activities
- journal objects
- teacher sets new action tag "Next Topic" according to the teaching plan and adds:
- new activities for that topic
- journal objects to show students new topic on examples
- teacher creates last action the lesson - "Home work" and
- inherit activities form the 2nd one
- creates seed object with that activity with useful initial state
During the class: