Karma/Collaboration

2009-07-31T04:14:13Z

Subzero:

<noinclude>{{GoogleTrans-en}}{{TOCleft}}</noinclude>

== Objective ==
To provide a mechanism to enable collaboration using JavaScript. On this way, we'll be able to support collaboration on Karma lessons.

== Use cases ==
Examples:
* A simple chat (over an html file), where you can see connected children to the activity and talk each other.

* Let's imagine a lesson: "Learning basic arithmetic", on this lesson we touch the topics: add, rest and multiply a number. At the end of the lesson we got the "Test". Here on "Test" one child writes a basic equation and challenges other child to solve it, then switch turns.

== The problem ==
How to create an easy way to write collaborative JavaScript to be run client-side in browsers.

== Keep in mind ==
* JavaScript has no model for distributed collaboration.
* Shared data can be considered volatile.

== Possible solutions ==
It would be ideally as simple as possible and as web-like as possible.

lucian has suggested 2 possible ways[http://honeyweb.wordpress.com/2009/07/29/generating-files-from-web-apps/]:
* Starting local servers in each Browse and using XMLHttpRequest(XHR) to send data between.
* Adding an API for this in window.sugar and using the existing Sugar collaboration Python API as a backend.

bemasc
* a DNS server and httpd server on each client. (example WikiBrowse )

m_stone:
* name the people with one wishes to collaborate with using:
** Telepathy
** DNS
** D-Bus to telepathy

* a way to get those names to the JS.
** D-Bus to telepathy
** HTTP to a webserver to D-Bus to telepathy

* data transfer via:
** D-Bus + Telepathy
** a central relay webserver
** point-to-point HTTP links to peer webservers.

Collaboration data:
Bemasc has suggested to store the messages using files and directories
/users could be a list of current users
/$USERNAME/ could be a list of messages, displayed as files
To check for new messages, just poll the contents of /$USERNAME/.
To check for new users, just poll /users.
If you want to see what messages $USERNAME has emitted, poll /$USERNAME/

Also one other way is using http PUT & GET

[[Category:GSoC]]

Karma/Collaboration

2009-07-30T19:46:06Z

Subzero:

2009-05-12T13:15:26Z

Subzero:

[[Image:Karma.png|right]]

[[Karma]] is a yet-to-be-created framework for creating very simple Sugar activities using javascript and html5. Karma relies extensively on the [http://www.jquery.com jQuery javascript library]. It is not intended to create powerful animations, simulations, or reusable artifacts. PyGTK and pygame are much better tools for those purposes. Check out the [http://karmaproject.wordpress.com Karma Project blog] for updates.

== Team ==

Felipe Lopez Toledo "SubZero" is creating a prototype for Karma as a Google Summer of Code project. [[USER:BryanWB| Bryan Berry]] is serving as his mentor.

== Project Requirements ==

* Create a single prototype activity which could be used as a template for sugarizing AJAX activities. The GSoC participant should not create her own activity but recreate an existing activity such as one of [http://www.pustakalaya.org/external-content/static/epaath/E-Paath-2.activity/activity/Activity/MenuStage.html OLE Nepal's flash activities].
* This prototype should have the following features:
** Simple interactive animation and audio using html5 tags like <canvas> and <audio>
** An assessment section that stores results of student's progress and gives them suggestions on improvement. Assessment info should be persistent.
** Has embedded pdf or pdf like document reader for activity lesson plan and teacher notes.
** Integrates with the Journal
** Navigation and Help elements, ideally reusing widgets from [http://www.jquery.com jQuery]
** Some element of collaboration using Telepathy (This could be really hard, depending on the state of javascript bindings to dbus)

== Technical Architecture ==

*ToDo* need to update this

Karma will work with basic functionality on any W3C standards-compliant browser. This notably excludes Microsoft's Internet Explorer. Karma will be particularly tailored to work within Sugar's [[Browse]] activity. Longer-term we hope to extend Karma to take advantage of Sugar's collaboration features.

Karma depends heavily the javascript library jQuery, version 1.3. Karma may end up using a subset of the jQuery UI library.

jQuery currently lacks full animation support but there are a number of other projects underway to create that functionality. For this reason, Karma will extend jQuery when we need to add new animation functionality rather than creating independent libraries. This should ease collaboration with others working on animation support for jQuery and ease possible integration/merging later.

Possible Underlying Components:
* Karma will work with any modern standards-based browser (this notably excludes Internet Explorer). Animation performance will be significantly better usin one of the latest javascript engines such as [http://en.wikipedia.org/wiki/V8_(JavaScript_engine) Google Chrome's v8 javascript engine], Mozilla's tracemonkey, or SquirrelFish.
* Google Gear's Filesystem API because it seems to have the most traction in the linux world
* Some mechanism to support dbus events

=== Conventions ===

* [[Karma:Anatomy_of_Lesson|Anatomy of a Karma Lesson]]
* Source Code stored here ? somewhere on git.sugarlabs.org
* Project Documentation kept in the SugarLabs wiki
* Code naming conventions ?
* file naming conventions ?

== Meetings ==

# Regular meeting between Felpe and Bryan every Tuesday 0200 UTC at #sugar on irc.freenode.net
# General GSOC meeting for participants from Sugar every Tuesday 1400 UTC #sugar-meeting

Meeting Notes
* [[Karma:Meeting 12 May 2009]]

== Project Plan ==

There are roughly 4 parts to this project plan: first get titanium running on the XO, second create a very simple learning activity with javascript and html5, third get that activity running on the XO in a roughly sugarized version of titanium, fourth extend the activity to take advantage of Sugar-specific features such as the Journal and Collaboration.

Before GSoc - May 22:
* get familiar with Sugar
* get familiar with html5
* Felipe to acquire XO
* learn more about java script
* select the appropriate js framework

May 23 - June 5:
“Karming” some simple OLE nepal activity w/out fs access, dbus, i8n

June 6:
Publish a blog post with the karmified activity. The report must include the problems I found, the ideas on how to solve those problems and timeline for rest of project. This post may elicit responses w/ solutions to important problems.

June 7 - June 12:
* Developing the first Karma widget (easy animation tool, boost animation tool from the selected js framework)
* Getting familiar with Sugar/Browse code

June 13 - July 12:
* Providing Karma + audio
* Providing Karma + client-side i18n
* Developing an activity template for Karma
* Changing the original activity to include above features

July 13:
Publish blog post that showcases updated activity. Explain problems encountered, what works, what still doesn’t.

July 15 - July 25:
* Fixing bugs
* Work on gears+karma support

July 26 - July 31:
* Documenting examples
* Improving documentation

August 1 - August 9: time for any eventual emergencies

== Project Risks ==

# Creating interactive animations with html5 and javascript is very new technology as html5 is a new standard. It could be much harder to create animations than we expect. Risk Level: High
# Javascript animations could be very slow on the XO. Risk Level: Low, we don't need very complex animations
# It could be very difficult to interface titanium with telepathy. Risk Level: High
# The Browse Sugar activity uses the spidermonkey javascript interpreter, which is not optimized for hmtl5. Karma's animations may be prohibitively slow in Browse and require a version of Browse that includes the newer tracemonkey javascript interpreter.

2009-04-02T13:50:53Z