359
edits
Changes
no edit summary
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.
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
* 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 ==
== Project Risks ==