Taxonomy: Difference between revisions
m remove commented-out ascii art (it's in the history) |
reorder layer sections to match diagram |
||
| Line 11: | Line 11: | ||
==Stack Components== | ==Stack Components== | ||
=== | ===Starch(es): A complete disk image for Sugar=== | ||
''(starch is composed of multiple sugars bonded together)'' | |||
Description: We often distribute complete disk images for Sugar, ready to | |||
boot. These images are composed of multiple elements of the above stack. | |||
Each image series should be named separately, to minimize confusion. For cutesy codenames, we could have a development build ("glycogen", a starch used to produce Glucose) and a stable build ("cellulose", an extremely stable starch). | |||
* In July 2010, Paraguay Educa chose the name '''[[Dextrose|Dextrose]]''' (approximately acronymized from "DEployments' Xo OS") for their release of Sugar 0.88 on Fedora 11 for XO laptops ([http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01213.html announcement]). The molecule [[wikipedia:Dextrose|Dextrose]] is the dextrorotatory form of glucose or D-glucose, the sugar in blood and other living systems. So, it represents a vital infusion for the project. | |||
===Honey: activities developed by 'in the wild' vendors=== | |||
''a sweet fluid made by bees, mostly Fructose'' | |||
Description: Activities that are packaged by outside developers, sometimes ports of activities to Sugar from other OS. It might enhance Sugar and the Sweet experience, but "honey frequently contains dormant endospores of the bacterium Clostridium botulinum, which can be dangerous to infants" [http://en.wikipedia.org/wiki/Honey Wikipedia]. | |||
~ For example, Skype, printer capability, IM software | |||
: as a former beekeeper I can tell you that not all honey is organic, though we all wish it were so (antibiotics taint a lot of it, especially in developing countries) [[User:Yamaplos|Yamaplos]] 15:04, 17 May 2008 (UTC) | |||
===Sucrose: The interface, plus a set of demonstration activities=== | |||
''("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined)'' | |||
Description: Sucrose consists of both Glucose and Fructose. It therefore | |||
represents a complete example Sugar environment, ready to be installed | |||
through a package manager. The purpose of Sucrose is so that prospective | |||
deployers can install the "sugar-sucrose" package, and immediately say | |||
"Wow! Look at all the cool capabilities that this system has!". | |||
===Glucose: The base Sugar environment=== | ===Glucose: The base Sugar environment=== | ||
| Line 43: | Line 66: | ||
features. Fructose may also serve as an example for people constructing | features. Fructose may also serve as an example for people constructing | ||
their own Activity sets. | their own Activity sets. | ||
===Ribose: The operating system components developed for Sugar=== | ===Ribose: The operating system components developed for Sugar=== | ||
| Line 64: | Line 77: | ||
to install Glucose if it has not yet been installed. | to install Glucose if it has not yet been installed. | ||
== | == Related concepts == | ||
===Sweet: The abstract design of the experience=== | |||
''(the taste of sugar)'' | |||
Description: "Sweet" is the abstract design of the interface's appearance | |||
and behavior, independent of any code actually implementing this design, and by extension—the learner experience. | |||
The mockups at [[Design Team/Designs]] represent this | |||
component's second major release, or perhaps 2.0-alpha. | |||
===Galactose: a future Sugar base designed for alternate computing forms=== | ===Galactose: a future Sugar base designed for alternate computing forms=== | ||