Changes

Karma (view source)

Revision as of 01:18, 10 May 2009

53 bytes removed , 01:18, 10 May 2009

Line 22: Line 22:

*ToDo* need to update this

−

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

+

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.

−

~~Preferred~~ Underlying Components:

+

Karma's primary software dependency is currently the jQuery 1.3 library.

−

* ~~[http://www~~.~~webkit.org Webkit] for html rendering engine rather than gecko~~

+

−

* [http://en.wikipedia.org/wiki/V8_(JavaScript_engine) Google Chrome's v8 javascript engine] ~~-- Note:~~ Mozilla's tracemonkey ~~offers comparable performance -- Note: Sorry~~, ~~but TM doesn't even compare to~~ SquirrelFish

+

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

−

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.

Line 40: Line 39:

* Code naming conventions ?

* file naming conventions ?

−

== Meetings ==

BryanWB

359

edits