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

== In this release ==

== In this release ==

This is the initial release and has missed some critical points for Sugar, e.g., a GUI to launch activities using Sweets. The major purpose for this release is exposing the fact that basic ideas and core implementations are mature enough to make Sweets useful in some [[#Try_the_release|workflows]] and to involve more people in Sweets and Sweets related project development, e.g., a la Ubuntu AppCenter for Sugar.

This is the initial release and has missed some critical points for Sugar, e.g., a GUI to launch activities using Sweets. The major purpose for this release is exposing the fact that basic ideas and core implementations are mature enough to make Sweets useful in some [[#Try_the_release|workflows]] and to involve more people in Sweets and Sweets related project testing and development, e.g., a la Ubuntu AppCenter for Sugar.

== Getting the release ==

== Getting the release ==

== Try the release ==

== Try the release ==

To try Sweets in practice, run several Sugar versions. On the Sweets level, there are not any restrictions to using Sweets on any GNU/Linux distribution. Successful usage depends only on the presence of PackageKit and the quality of sweet packages (sweets). For now, sugar sweets are well aware of Fedora, Debian/Ubuntu and Gentoo package names and not so well aware of openSUSE and Mandriva. Sugar sweets launchs were tested on some recent Fedora and Ubuntu releases. The quality of other GNU/Linux distribution support depends only on how often Sweets is used on these distributions and the reporting of problems by the community.

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.

 

Note, Sugar Shell does not start the authentication agent, and preparing sugar start can be processed only in a Desktop Environment, e.g., Gnome. To launch a recent stable Sugar version in emulator mode, type in a terminal:

 

 

 

 

After that, it is possible to run Sugar via sweets from the [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|X session]].

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

* Zero Install development team to take care about reviewing the code that was introduced by Sugar workflow needs.

* Zero Install development team to take care about reviewing the code that was introduced by Sugar workflow needs.

* People who pointed Open Build System out, Jigish Gohil and David Van Assche.

* People who pointed Open Build System out, Jigish Gohil and David Van Assche.

* People who initially tested Sweets and replied with useful feedback, Michael Stone, Rafael Ortiz, Sebastian Silva.

* People who initially tested Sweets and replied with useful feedback, Michael Stone, Rafael Ortiz, Sebastian Silva, Bernie Innocenti.

* The [[Infrastructure Team]] for their help with setting up services required for Sweets infra.

* The [[Infrastructure Team]] for their help with setting up services required for Sweets infra.

* The [[Wiki Team]] for continuous polishing of [[Platform_Team/Sweets|Sweets]] wiki pages.

* The [[Wiki Team]] for continuous polishing of [[Platform_Team/Sweets|Sweets]] wiki pages.

* [http://activitycentral.com/ Activity Central] for supporting the work on the 1.0 release final phase.

* [http://activitycentral.com/ Activity Central] for supporting the work on the 1.0 release final phase.