Karma: Difference between revisions

Line 49:

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.

~~# Apply for the GSoC program formally~~

Before GSoc - May 22:

~~# Get a "Hello World" Titanium app running on the XO and measure its system footprint. Compare it with regular Firefox~~

* get familiar with Sugar

~~# Select an existing [http~~:~~//www.pustakalaya.org/external-content/static/epaath/E-Paath-2.activity/activity/Activity/MenuStage.html E-Paath] flash activity to reengineer with javascript and html5.~~

* get familiar with html5

#* ~~The activity should have interactive animation and sound using javascript and html5~~

* learn more about java script

~~#* Layout the strings in the activity so that they are compatible~~ with ~~pootle~~

* select the appropriate js framework

#* ~~Determine possible ways to add collaboration.~~

~~# Recreate the learning activity~~ with ~~javascript and~~ html5

~~# Get the activity to run successfully on Titanium and on firefox. Let's ignore Internet Explorer because it does not support html5~~

~~# Integrate the activity with the Journal~~

~~# Extend the activity so that it has some collaboration features~~

~~# Document~~ the ~~resulting code and issues encountered so that others can build on this project.~~

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

@@ Line 49: / Line 49: @@
 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.
-# Apply for the GSoC program formally
+Before GSoc - May 22:
-# Get a "Hello World" Titanium app running on the XO and measure its system footprint. Compare it with regular Firefox
+* get familiar with Sugar
-# Select an existing [http://www.pustakalaya.org/external-content/static/epaath/E-Paath-2.activity/activity/Activity/MenuStage.html E-Paath] flash activity to reengineer with javascript and html5.
+* get familiar with html5
-#* The activity should have interactive animation and sound using javascript and html5
+* learn more about java script
-#* Layout the strings in the activity so that they are compatible with pootle
+* select the appropriate js framework
-#* Determine possible ways to add collaboration.
-# Recreate the learning activity with javascript and html5
-# Get the activity to run successfully on Titanium and on firefox. Let's ignore Internet Explorer because it does not support html5
-# Integrate the activity with the Journal
-# Extend the activity so that it has some collaboration features
-# Document the resulting code and issues encountered so that others can build on this project.
+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 ==