359
edits
Changes
Jump to navigation
Jump to search
Line 18:
Line 18: + + + + + + + + + + + + + + +
no edit summary
** Some element of collaboration using Telepathy (This could be really hard, depending on the state of javascript bindings to dbus)
** Some element of collaboration using Telepathy (This could be really hard, depending on the state of javascript bindings to dbus)
== Initial Thoughts on Technical Architecture ==
It is preferable to use a minimalist html rendering engine, javascript compiler, and filesystem access API rather than extending full-blown browser such as Mozilla.
Preferred Underlying Components:
* Webkit for html rendering engine rather than gecko
* Google Chrome's v8 javascript compiler -- Note: Mozilla's tracemonkey offers comparable performance
* Google Gear's Filesystem API because it seems to have the most traction in the linux world
* Some mechanism to support dbus events
At this time, 23 March 2009, [http://www.titaniumapp.com Titanium] seems to offer all of the above but warrants testing. On the XO. Other options are to use regular firefox, Epiphany, or another browser. Titanium's developers have expressed enthusiasm for extending their platform to better support Sugar.
== Project Plan ==
== 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.
# Apply for the GSoC program formally
# Get Titanium running on the XO and measure its system footprint. Compare it with regular Firefox
#