Changes

Hopefully you've read the [[Taxonomy]] page and all of this will make sense to you already.  If you want an XO laptop to run Sugar (or to use SoaS), you will need to translate matched pairs of Glucose and Fructose projects (i.e. Glucose/Fructose or Glucose 0.82/Fructose 0.82).

Hopefully you've read the [[Taxonomy]] page and all of this will make sense to you already.  If you want an XO laptop to run Sugar (or to use SoaS), you will need to translate matched pairs of Glucose and Fructose projects (i.e. Glucose/Fructose or Glucose 0.82/Fructose 0.82).

Selecting a matched pair of Glucose and Fructose projects to start working on should be done carefully and with a clear understanding of what Sugar version will be used in the deployment.  For many XO deployments, Sugar version 0.84 may be the latest stable version that loads easily on the XO (although work continues on porting/adapting newer versions of Sugar to run on the XO laptop).

Selecting a matched pair of Glucose and Fructose projects to start working on should be done carefully and with a clear understanding of what Sugar version will be used in the deployment.  For many XO deployments, Sugar version 0.84 may be the latest stable version that loads easily on the XO (although work continues on porting/adapting newer versions of Sugar to run on the XO 1.0 and 1.5 laptops).

The good news is that while some strings have moved around with restructuring of the code, many, many of the Sugar UI strings remain the same from release to release.  

The good news is that while some strings have moved around with restructuring of the code, many, many of the Sugar UI strings remain the same from release to release.