Difference between revisions of "Education Project/Effort/Various adaptations on Sugar"
From Apache OpenOffice Wiki
< Education Project | Effort
(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 *...) |
B michaelsen (Talk | contribs) |
||
(13 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | <font color=red> '''Draft''' </font | + | <font color=red> '''Draft''' </font> |
+ | |||
+ | [[Education_Project/Effort/Various_adaptations_on_Sugar/Work_In_Progress| => Current work in Progress (what students are doing at the moment)]] | ||
+ | |||
Line 8: | Line 11: | ||
* create Valgrind use with OpenOffice.org and assimilated documentation | * create Valgrind use with OpenOffice.org and assimilated documentation | ||
* create school cases | * create school cases | ||
− | |||
− | + | Phase 1 : preliminary | |
− | + | ||
− | + | * Install the tools | |
+ | * Compile OpenOffice.org | ||
+ | * Then compile OOo4Kids | ||
+ | * Document Valgrind and gdb use and tracing | ||
Phase 2 "Sugarisation" | Phase 2 "Sugarisation" | ||
− | + | * Present Sugar (and document what is important in the study) | |
+ | * Adapt OOo4Kids to the '''XO''' machines, and to the '''Sugar OS''' | ||
+ | * Describe 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 speed 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 | Phase 4 UI | ||
− | 3) | + | 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. | |
+ | [[Category:Education]] |
Latest revision as of 23:11, 24 February 2010
Draft
=> Current work in Progress (what students are doing at the moment)
FIXME :
- create a planning
- create a Gantt diagram
- create Valgrind use with OpenOffice.org and assimilated documentation
- create school cases
Phase 1 : preliminary
- Install the tools
- Compile OpenOffice.org
- Then compile OOo4Kids
- Document Valgrind and gdb use and tracing
Phase 2 "Sugarisation"
- Present Sugar (and document what is important in the study)
- Adapt OOo4Kids to the XO machines, and to the Sugar OS
- Describe 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 speed 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.