Features/Smart Objects/Shared Actions: Difference between revisions

Line 9:

** 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

# object + tag + time = action, i.e., each action has duration

- everything is on server

# everything is on server

- objects and actions might have tags

# objects and actions might have tags

- parental relationships for actions, action threads

# parental relationships for actions, action threads

- the same objects might be used in several actions,

# the same objects might be used in several actions, objects have different states associated with different actions - object's history.

objects have different states associated with different

# all (j)object are composite, they have different history for different users

actions - object's history.

# 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

- all (j)object are composite, they have different history

# two views for the same action, one for students (viewer/actor) and one for teachers (initiator/moderator)

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"

# new action will be automatically inherit objects:

# * teacher himself

#* teacher himself

# * students

#* students

# 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:

# * action tags

#* action tags

# * activities

#* activities

# * journal objects

#* journal objects

# 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

# inherit activities form the 2nd one

@@ Line 9: / Line 9: @@
 ** 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
-# object + tag + time = action, i.e., each action has duration
+- everything is on server
-# everything is on server
+- objects and actions might have tags
-# objects and actions might have tags
+- parental relationships for actions, action threads
-# parental relationships for actions, action threads
+- the same objects might be used in several actions,
-# the same objects might be used in several actions, objects have different states associated with different actions - object's history.
+  objects have different states associated with different
-# all (j)object are composite, they have different history for different users
+  actions - object's history.
-# 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
+- all (j)object are composite, they have different history
-# two views for the same action, one for students (viewer/actor) and one for teachers (initiator/moderator)
+  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"
 # new action will be automatically inherit objects:
-# * teacher himself
+#* teacher himself
-# * students
+#* students
 # 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:
-# * action tags
+#* action tags
-# * activities
+#* activities
-# * journal objects
+#* journal objects
 # 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
 # inherit activities form the 2nd one