Educational Toolkit: Difference between revisions

(4 intermediate revisions by the same user not shown)

Line 141:

The software is being developed in Python with emphasis on easy User Interface. The software will use : PyGTK for User Interface; Telepathy and DBus Tubes for connectivity; XML DOM API for xml

I will be reusing widgets. For instance, the Write activity uses the abiword widget from pyabiword and the Browse activity uses the gecko widget from hulahop. I will also ~~try~~ to ~~write widgets~~ to ~~get functionality from other existing activites if desired~~. ~~(Stretch Goal)~~

I will be reusing widgets. For instance, the Write activity uses the abiword widget from pyabiword and the Browse activity uses the gecko widget from hulahop.

The major work in this project is to provide a consistent method to share information over the mesh network. Currently, there are three scenarios which need to be supported:

#Unicast

#GroupCast

#Broadcast

D-Bus provides signals and methods:

* Signals are multicast - they are sent to all participants in the shared activity (including the sender). They send data and have no return value.

* Method calls are called on a single participant, and they do have a return value.

We can either use them as illustrated by the HelloMesh Activity directly or we can use their wrappers written by olpcgames folder in the package olpcgames.mesh . This package contains functions like Unicast, Broadcast, lookupBuddy, myHandle etc. which can be used as-is.

The Sugar.Presence Service will also be imported to find out our own name(owner's name), buddies around you and shared activites.

TALK : Another interesting idea can be its integration with GroupThink later which is another GSoC Project, but I am not very familiar with all its details. -Deepank

Please find some of the diagrams shown below to aid in implementation of the project :

Image:EducationalToolkit MVC.png|Standard MVC Model

Image:EducationalToolkit_Model.jpg|Model Component

Image:EducationalToolkit_Controller.jpg|Controller Component

Image:EducationalToolkit_UseCase.png|UseCase diagram

</gallery>

----

Line 191:

Line 221:

'''July 21 - July 28 : '''

~~Integrate the Question and Answer Package so as to make~~ it ~~a forum post on~~ Moodle ~~Servers. According to Martin, Moodle has been already integrated and authenticated with Sugar.~~

Do feasibility study of integrating it with Moodle

'''July 29 - August 5 : '''

Work on documentation ~~and integrate the activity with Moodle.~~

Work on documentation

~~'''August 5 - August 10 : '''~~

~~Port the activity on Windows also.~~

'''August 10 - August 17 : '''

'''August 5 - August 17 : '''

Internal Alpha release cycle.

@@ Line 141: / Line 141: @@
 The software is being developed in Python with emphasis on easy User Interface. The software will use : PyGTK for User Interface; Telepathy and DBus Tubes for connectivity; XML DOM API for xml
-I will be reusing widgets. For instance, the Write activity uses the abiword widget from pyabiword and the Browse activity uses the gecko widget from hulahop. I will also try to write widgets to get functionality from other existing activites if desired. (Stretch Goal)
+I will be reusing widgets. For instance, the Write activity uses the abiword widget from pyabiword and the Browse activity uses the gecko widget from hulahop.
+The major work in this project is to provide a consistent method to share information over the mesh network. Currently, there are three scenarios which need to be supported:
+#Unicast
+#GroupCast
+#Broadcast
+D-Bus provides signals and methods:
+* Signals are multicast - they are sent to all participants in the shared activity (including the sender). They send data and have no return value.
+* Method calls are called on a single participant, and they do have a return value.
+We can either use them as illustrated by the HelloMesh Activity directly or we can use their wrappers written by olpcgames folder in the package olpcgames.mesh . This package contains functions like Unicast, Broadcast, lookupBuddy, myHandle etc. which can be used as-is.
+The Sugar.Presence Service will also be imported to find out our own name(owner's name), buddies around you and shared activites.
+TALK : Another interesting idea can be its integration with GroupThink later which is another GSoC Project, but I am not very familiar with all its details. -Deepank
+Please find some of the diagrams shown below to aid in implementation of the project :
+<gallery>
+Image:EducationalToolkit MVC.png|Standard MVC Model
+Image:EducationalToolkit_Model.jpg|Model Component
+Image:EducationalToolkit_Controller.jpg|Controller Component
+Image:EducationalToolkit_UseCase.png|UseCase diagram
+</gallery>
 ----
@@ Line 191: / Line 221: @@
 '''July 21 - July 28 : '''
-Integrate the Question and Answer Package so as to make it a forum post on Moodle Servers. According to Martin, Moodle has been already integrated and authenticated with Sugar.
+Do feasibility study of integrating it with Moodle
 '''July 29 - August 5 : '''
-Work on documentation and integrate the activity with Moodle.
+Work on documentation
-'''August 5 - August 10 : '''
-Port the activity on Windows also.
-'''August 10 - August 17 : '''
+'''August 5 - August 17 : '''
 Internal Alpha release cycle.