2. Making the installation of Activities easier: Dave Farning is working on a web interface to managing activities based upon Mozilla's AMO codebase (addons.mozilla.org). He has successfully used AMO on a local server to install activities on an XO-1 laptop and to install Sugar on a conventional laptop. He has started submitting a series of patches upstream to Mozilla.org with the goal that SugarLabs will be able to use the AMO codebase as maintained by Moxilla. A few areas that require work: (a) Look and feel – applying the sugarlabs stylesheets; (b) Applications – currently, AMO hardcodes application data rather than handled dynamically; (c) Addontypes – AMO can handle several addontypes such as extension, plugins, and and dictionaries, but they are not yet handled dynamically. By modularizing how AMO handles applications and add-on types, we should be able to drop in Sugar application and and addontype code. | 2. Making the installation of Activities easier: Dave Farning is working on a web interface to managing activities based upon Mozilla's AMO codebase (addons.mozilla.org). He has successfully used AMO on a local server to install activities on an XO-1 laptop and to install Sugar on a conventional laptop. He has started submitting a series of patches upstream to Mozilla.org with the goal that SugarLabs will be able to use the AMO codebase as maintained by Moxilla. A few areas that require work: (a) Look and feel – applying the sugarlabs stylesheets; (b) Applications – currently, AMO hardcodes application data rather than handled dynamically; (c) Addontypes – AMO can handle several addontypes such as extension, plugins, and and dictionaries, but they are not yet handled dynamically. By modularizing how AMO handles applications and add-on types, we should be able to drop in Sugar application and and addontype code. |