Difference between revisions of "Education Project/Effort/Various adaptations on Sugar"

From Apache OpenOffice Wiki
Jump to: navigation, search
(New page: <font color=red> '''Draft''' </font FIXME : * create a planning * create a Gantt diagram * create Valgrind use with OpenOffice.org and assimilated documentation * create school cases *...)
 
Line 10: Line 10:
 
* french below -> must be translated into english  
 
* french below -> must be translated into english  
  
Installation des outils
+
Phase 1 : preliminary
Compilation d'OpenOffice.org
+
 
Compilation d'OOo4Kids
+
* Install the tools
 +
* Compile OpenOffice.org
 +
* then compile OOo4Kids
 +
 
  
 
Phase 2  "Sugarisation"
 
Phase 2  "Sugarisation"
  
1) adapter Ooo4Kids aux machines de type " XO ", et a l'OS "Sugar"
+
* Present Sugar (and document what is important in the study)
 +
* Adapt OOo4Kids to the '''XO''' machines, and to the '''Sugar OS'''
 +
* escribe the specs to transform an single application in an installable application, everything under Sugar (packaging, tools, to do)
  
Présenter Sugar.
+
Phase 3 Profiling ( working on OOo4Kids only)
Quelles sont les spécifications pour transformer une application autonome "un Bundle" en une application installable avec Sugar (packetage, outils, mise en oeuvre)
+
  
Phase 3 Profiling ( Travail sur OOo4Kids )
+
* Present Valgrind (on Linux)
 +
* Present some examples of Valgrind use
 +
* Improve the spee of the software regarding its perfs ( cold startup, precise trace at execution time ... and so on)
 +
* Application to OOo4Kids : based on a case study where 100%  of load is measured at opening, present at least one measurable improvement per students. Better: if the changes can be backported to OOo.
  
2) ameliorer la vitesse du logiciel au niveau de ses performances (demarrage a froid, trace poussee du binaire a l'execution)
 
  
Outils : gdb, gcc , g++ , Valgrind  
+
Tools : gdb, gcc , g++ , Valgrind  
  
  
Presentation de Valgrind, exemples d'utilisation
 
Application à OpenOffice.org : ouverture d'un document qui met le système à plat ( 100%  de charge pendant l'ouverture)
 
  
Présentation d'une amélioration mesurable et justifiée (si le changement est portable dans OOo, c'est encore mieux)
 
  
 
Phase 4  UI  
 
Phase 4  UI  
  
3) travailler a ameliorer l'interface utilisateur
+
3) Work on improve the UI
  
 +
* User Interface discovery
 +
* describe how menus work, same for toolbars
  
Découverte de l'interface utilisateur : comment marchent les menus, et le barres d'outils
+
Objective : one validated, or defined in a spec, improvement per student is expected.
  
Une amélioration par étudiant, qui peut être celle demandée par un enseignant, sinon défini dans une spec.
+
Example : add a password in the prefs, to avoid children modifying everything
Exemple : implémentation du mote de passe dans les prefs
+
  
  
Rapport : fait en continu, sur le wiki sur page person (je vais créer les pages pour le nouveau sujet.
+
'''Report''' : made continuously, this ddocument must be made in english.

Revision as of 21:22, 5 July 2009

Draft must be translated into english

Phase 1 : preliminary

  • Install the tools
  • Compile OpenOffice.org
  • then compile OOo4Kids


Phase 2 "Sugarisation"

  • Present Sugar (and document what is important in the study)
  • Adapt OOo4Kids to the XO machines, and to the Sugar OS
  • escribe the specs to transform an single application in an installable application, everything under Sugar (packaging, tools, to do)

Phase 3 Profiling ( working on OOo4Kids only)

  • Present Valgrind (on Linux)
  • Present some examples of Valgrind use
  • Improve the spee of the software regarding its perfs ( cold startup, precise trace at execution time ... and so on)
  • Application to OOo4Kids : based on a case study where 100% of load is measured at opening, present at least one measurable improvement per students. Better: if the changes can be backported to OOo.


Tools : gdb, gcc , g++ , Valgrind



Phase 4 UI

3) Work on improve the UI

  • User Interface discovery
  • describe how menus work, same for toolbars

Objective : one validated, or defined in a spec, improvement per student is expected.

Example : add a password in the prefs, to avoid children modifying everything


Report : made continuously, this ddocument must be made in english.

Personal tools