Difference between revisions of "Karma/To-Do"

From Sugar Labs
Jump to: navigation, search
(Christoph)
Line 10: Line 10:
 
** according to dsd we can simply include a LICENSE file in the top-directory and declare on a directory basis which licenses apply (jquery under MIT and GPL, Karma js code under MIT ''(?)'' and multimedia assets under CC-BY-SA)
 
** according to dsd we can simply include a LICENSE file in the top-directory and declare on a directory basis which licenses apply (jquery under MIT and GPL, Karma js code under MIT ''(?)'' and multimedia assets under CC-BY-SA)
 
* investigate browser solution for Sugar .xo bundle
 
* investigate browser solution for Sugar .xo bundle
* ask Roxan re; Firefox Cache directory should be empty - how to do that and re: changes done to Firefox => (2009-07-13: will be done once Roshan returns on July 24)
 
 
* define requirements for browser for Sugar .xo bundles
 
* define requirements for browser for Sugar .xo bundles
 
** html 5 capable;-)
 
** html 5 capable;-)
Line 25: Line 24:
 
** http://opensource.sfsu.edu/node/654
 
** http://opensource.sfsu.edu/node/654
 
** http://seleniumhq.org/
 
** http://seleniumhq.org/
* [[Karma/Assessment| assessment]] brain storming
 
  
 
== Felipe ==
 
== Felipe ==

Revision as of 05:33, 18 August 2009

Bryan

  • clean up main karma repo
  • add getopt.js to karma.js
  • create dummy kindex.html w/ links to examples
  • bundle in a basic browser and functionality to create xo bundles

Christoph

  • investigate licensing questions (list of files declaring the license okay?) => (2009-07-21: contacted Andriani, will also do more research myself)
    • according to dsd we can simply include a LICENSE file in the top-directory and declare on a directory basis which licenses apply (jquery under MIT and GPL, Karma js code under MIT (?) and multimedia assets under CC-BY-SA)
  • investigate browser solution for Sugar .xo bundle
  • define requirements for browser for Sugar .xo bundles
    • html 5 capable;-)
    • integrate well with Sugar
      • on a visual level (or E-Paath fullscreen approach)
      • on a technical level: e.g. integration with Journal, DBUS, etc.)
    • candidates
      • Surf-106.xo
      • E-Paath brower (based on Firefox-6.xo)
      • custom HTML/JavaScript renderer (browse?)
      • browse on the early Fedora 11 based XO-1 images supports HTML 5
  • example of possible navigation and UI requirements
  • Web sites to be read:

Felipe

  • Get "Adding Up to 10" working
  • Add i18n to "Adding up to 10"