Features/Smart Objects/Shared Actions - Revision history

Alsroot: /* Journal objects */

2011-06-03T18:59:58Z

Journal objects

← Older revision		Revision as of 14:59, 3 June 2011
Line 29:		Line 29:
	=== Journal objects ===		=== Journal objects ===

	Objects that were ~~created~~ in process of using Shared Actions. After being initially created, such objects will be singular, i.e., if teacher created an Calculate activity object "How to learn tangent function", all students will work with the same object but server will keep (implicitly) per student copies of "How to learn tangent function" object and any particular student will see only his own copy but teacher will manage to see all variants to track what students do.		Objects that were used in process of using Shared Actions. After being initially created, such objects will be singular, i.e., if teacher created an Calculate activity object "How to learn tangent function", all students will work with the same object but server will keep (implicitly) per student copies of "How to learn tangent function" object and any particular student will see only his own copy but teacher will manage to see all variants to track what students do.

	Shared objects' state might be also per action, i.e., all shared objects might be reused in several actions. For example, "How to learn tangent function" might be used in two actions, the action that represents class time when teacher explained the topic and in another action that represents student's home work that was given by teacher in the class. In all cases "How to learn tangent function" is the same object but it has two sorts of states, for class time action and for home work action. Such per-action behaviour might be useful since it represents learning process history.		Shared objects' state might be also per action, i.e., all shared objects might be reused in several actions. For example, "How to learn tangent function" might be used in two actions, the action that represents class time when teacher explained the topic and in another action that represents student's home work that was given by teacher in the class. In all cases "How to learn tangent function" is the same object but it has two sorts of states, for class time action and for home work action. Such per-action behaviour might be useful since it represents learning process history.

Alsroot: /* Journal objects */

2011-06-03T18:58:07Z

Journal objects

← Older revision		Revision as of 14:58, 3 June 2011
Line 31:		Line 31:
	Objects that were created in process of using Shared Actions. After being initially created, such objects will be singular, i.e., if teacher created an Calculate activity object "How to learn tangent function", all students will work with the same object but server will keep (implicitly) per student copies of "How to learn tangent function" object and any particular student will see only his own copy but teacher will manage to see all variants to track what students do.		Objects that were created in process of using Shared Actions. After being initially created, such objects will be singular, i.e., if teacher created an Calculate activity object "How to learn tangent function", all students will work with the same object but server will keep (implicitly) per student copies of "How to learn tangent function" object and any particular student will see only his own copy but teacher will manage to see all variants to track what students do.

	Shared objects' state might be also per action, i.e., all shared objects might be reused in several actions. For example, "How to learn tangent function" might be used in two ~~sessions~~, the action that represents class time when teacher explained the topic and in another action that represents student's home work that was given by teacher in the class. In all cases "How to learn tangent function" is the same object but it has two sorts of states, for class time action and for home work action. Such per-action behaviour might be useful since it ~~represent~~ learning process history.		Shared objects' state might be also per action, i.e., all shared objects might be reused in several actions. For example, "How to learn tangent function" might be used in two actions, the action that represents class time when teacher explained the topic and in another action that represents student's home work that was given by teacher in the class. In all cases "How to learn tangent function" is the same object but it has two sorts of states, for class time action and for home work action. Such per-action behaviour might be useful since it represents learning process history.

	=== Tags ===		=== Tags ===

Alsroot: /* Journal objects */

2011-06-03T18:57:02Z

Journal objects

← Older revision		Revision as of 14:57, 3 June 2011
Line 29:		Line 29:
	=== Journal objects ===		=== Journal objects ===

	Objects that were created in process of using Shared Actions.		Objects that were created in process of using Shared Actions. After being initially created, such objects will be singular, i.e., if teacher created an Calculate activity object "How to learn tangent function", all students will work with the same object but server will keep (implicitly) per student copies of "How to learn tangent function" object and any particular student will see only his own copy but teacher will manage to see all variants to track what students do.

			Shared objects' state might be also per action, i.e., all shared objects might be reused in several actions. For example, "How to learn tangent function" might be used in two sessions, the action that represents class time when teacher explained the topic and in another action that represents student's home work that was given by teacher in the class. In all cases "How to learn tangent function" is the same object but it has two sorts of states, for class time action and for home work action. Such per-action behaviour might be useful since it represent learning process history.

	=== Tags ===		=== Tags ===

Alsroot: /* The purpose */

2011-06-03T17:15:42Z

The purpose

@@ Line 9: / Line 9: @@
 ** no need in special backup routines, everything is shared from the beginning and implicitly
-{{Show|Conception |<pre>
+== Conception ==
 - object + tag + time = action, i.e., each action has duration
 - everything is on server

Alsroot at 23:12, 2 June 2011

2011-06-02T23:12:01Z

← Older revision		Revision as of 19:12, 2 June 2011
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
	# 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"		# 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

Alsroot at 22:54, 2 June 2011

2011-06-02T22:54:05Z

@@ Line 9: / Line 9: @@
 ** no need in special backup routines, everything is shared from the beginning and implicitly
-== Conception ==
+{{Show|Conception|
 # object + tag + time = action, i.e., each action has duration
@@ Line 18: / Line 18: @@
 # 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
 == Teacher workflow ==
 == Students workflow ==

Alsroot at 20:27, 2 June 2011

2011-06-02T20:27:51Z

← Older revision		Revision as of 16:27, 2 June 2011
Line 8:		Line 8:
	** easy access for teachers to all students' work		** easy access for teachers to all students' work
	** 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

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

	== Teacher workflow ==		== Teacher workflow ==

	== Students workflow ==		== Students workflow ==

Alsroot: moved Features/Smart Objects/Class View to Features/Smart Objects/Shared Actions

2011-06-02T13:58:35Z

moved Features/Smart Objects/Class View to Features/Smart Objects/Shared Actions

← Older revision	Revision as of 09:58, 2 June 2011
(No difference)

Alsroot: Created page with "== 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 regu..."

2011-06-02T12:30:45Z

Created page with "== 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 regu..."

New page

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

== Teacher workflow ==

== Students workflow ==