Changes

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 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. 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.

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 being based on the [http://0install.net/why.html Zero Install] system.

=== To not reinvent the wheels ===

=== To not reinvent the wheels ===

== What is Sweets ==

== What is Sweets ==

So, Sweets is a [[wikipedia:Package_management_system |Package Management System]] based on [http://0install.net/ Zero Install], a decentralized, cross-distribution, software installation system. It is intended to distribute various software projects created in the Sugar ecosystem, such as libraries, sugar itself, and sugar activities.

So, Sweets is a [[wikipedia:Package_management_system |Package Management System]] entirely based on [http://0install.net/ Zero Install], a decentralized, cross-distribution, software installation system. It might be treated as a tools and infrastructure wrapper around Zero Install. Sweets is intended to distribute various software projects created in the Sugar ecosystem, such as libraries, sugar itself, and sugar activities.

This new distribution method is initiated assuming that:

This new distribution method is initiated assuming that:

The purpose is to create a new distribution method instead of reusing:

The purpose is to create a new distribution method instead of reusing:

# ''.xo bundles''

# [[Development_Team/Almanac/Activity_Bundles|''.xo bundles'']]

#* Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries.

#* Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries.

#* But, are not effective in supporting the use of multiple versions of software, e.g., the results of experiments (the work) of different doers, simultaneously. Users must manually handle the variety of activity versions, e.g., sort out all the local bundles or directories in {{Code|~/Activities}}.

#* But, are not effective in supporting the use of multiple versions of software, e.g., the results of experiments (the work) of different doers, simultaneously. Users must manually handle the variety of activity versions, e.g., sort out all the local bundles or directories in {{Code|~/Activities}}.

At the same time, existing distribution methods are reused in Sweets:

At the same time, existing distribution methods are reused in Sweets:

# ''.xo bundles'' is a subset of the Sweets workflow

# [[Development_Team/Almanac/Activity_Bundles|''.xo bundles'']] is a subset of the Sweets workflow, from usage point of view

#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.

#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.

# ''native packages''

# ''native packages''

== Try the release ==

== Try the release ==

There are Sugar Shell sweets as an example how to use Sweets in practice. See [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|Sweets Usage]] guide for instructions.

There are Sugar Shell sweets as an example of how to use Sweets in practice. See [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|Sweets Usage]] guide for instructions.

== Further reading ==

== Further reading ==

* support search among remote sweets on the client side,

* support search among remote sweets on the client side,

* provide an initial GUI for browsing local and remote sweets.

* provide an initial GUI for browsing local and remote sweets.

== Credits ==

== Credits ==