Educational Toolkit: Difference between revisions

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:

Line 152:

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

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

@@ 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:
@@ Line 152: / Line 152: @@
 * 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.
+Please find some of the diagrams shown below to aid in implementation of the project :
 <gallery>