Changes

== Retrospection ==

== Retrospection ==

Nearly 2 years have passed since the time of a meeting, between several Zero Install and Sugar people, occurred on the #sugar-meeting IRC channel. The meeting was organized by Michael Stone (if I'm wrong, he will correct me) to exchange knowledge and to learn whether Zero Install might be a good fit for use in Sugar activity installation. Thomas Leonard wrote a [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776 summary] and Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776/focus=18807 forwarded] it to sugar-devel mailing list.

Nearly 2 years have passed since the time of a meeting between several Zero Install and Sugar people on the #sugar-meeting IRC channel. That meeting was organized by Michael Stone (if I'm wrong, he will correct me) to exchange knowledge and to learn whether or not Zero Install might be a good fit for use in Sugar activity installation. Thomas Leonard wrote a [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776 summary] and Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776/focus=18807 forwarded] it to the sugar-devel mailing list.

The idea of using Zero Install in the Sugar ecosystem passed several mutations and, eventually, it seems to be that the core ideas have settled down and are ready to be presented widely in the community.

The idea of using Zero Install in the Sugar ecosystem passed several mutations and, eventually, it seems that the core ideas have settled down and are ready to be presented widely in the community.

== The pillars ==

== The pillars ==

=== Learning by doing ===

=== Learning by doing ===

The preeminent core idea behind Sugar is learning by doing. It is critical to Sugar to have the tools that support the doing metaphor well, doing not only within regular project teams, but also by individuals who tweak the software in the process of learning. And not the least of options is sharing the results of doer/learner experiments. Sweets is intended to make these aspects less annoying using the [http://0install.net/ Zero Install] system.

The preeminent core idea behind Sugar is learning by doing. Thus, it is critical to Sugar to have the tools that support the doing metaphor well, doing not only within regular activities and project teams, but also by individuals who tweak the software in the process of learning. And not the least of options is sharing the results of doer/learner experiments. Sweets is intended to make these aspects less annoying using the [http://0install.net/ Zero Install] system.

=== To not reinvent the wheels ===

=== To not reinvent the wheels ===

The details instructions can be found in [[Platform_Team/Guide/Sweets_Usage#Installation|Sweets Usage]] guide.

The details instructions can be found in [[Platform_Team/Guide/Sweets_Usage#Installation|Sweets Usage]] guide.

First, install the PackageKit package with the packages for integration with the Desktop Environment you are using, e.g., {{Code|gnome-packagekit}} for Gnome. It is important to install exactly integration package to have an authentication agent that depends on the particular Desktop Environment. After installation, it might be required to relogin from the Desktop Environment session.

First, install the PackageKit package with the packages for integration with the Desktop Environment you are using, e.g., {{Code|gnome-packagekit}} for Gnome. It is important to install the exact integration package required to have an authentication agent that depends on the particular Desktop Environment. After installation, it might be required to relogin from the Desktop Environment session.

Download and run Sweets installer:

Download and run Sweets installer: