10,505
edits
Changes
Jump to navigation
Jump to search
Line 24:
Line 24: − This feature + + + + + + + + + +
Features/Classroom management (view source)
Revision as of 12:02, 11 July 2013
, 12:02, 11 July 2013→Detailed Description
== Detailed Description ==
== Detailed Description ==
As described in the summary, the goal of this feature is to encapsulate three aspects of classroom management into one harmonious set of tools and interactions. The goal is to provide tools for visualization and exchange of Journal activity. We'd like to accomplish this within the context of the existing Sugar infrastructure (for reasons of maintainability) and do it in a way such that the teacher and child have maximum control of the flow of information and content.
There are four components to the work:
# capturing activity usage (this is already largely accomplished by the accumulation of launch times [https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/activity/activity.py#L332 1]). We may want to consider adding metadata which captures the accumulated time an activity is the top window in Sugar.
# visualizing activity usage (again, this is largely accomplished by Analyze Journal [http://activities.sugarlabs.org/en-US/sugar/addon/4545 2]). We may want to enhance the stats and also to maintain a current data object with these stats.
# exchange between the teacher and the student (largely accomplished by Journal Share [http://activities.sugarlabs.org/en-US/sugar/addon/4656 3]). We plan to expand upon Journal Share to enable automatic uploading of statistics from the student laptop. We also plan to add the ability to push a favorite view from the teacher's Sugar to the student's Sugar.
# exchange between the teacher and a webservice (this can leverage the webservices mechanism [[WebServices|4]] but needs to be informed by more clarity around what needs to be uploaded/downloaded
Above and beyond these components, we need to define a workflow by which they are used:
...
== Benefit to Sugar ==
== Benefit to Sugar ==