Difference between revisions of "Platform Team/Sweets Distribution/Factory/Features"

From Sugar Labs
Jump to navigation Jump to search
Line 1: Line 1:
 
== Users oriented ==
 
== Users oriented ==
  
The following features are oriented to end users
+
The following features are oriented to end users.
  
 
=== Sugar Network integration ===
 
=== Sugar Network integration ===
  
By default, Sugar Shell looks the same as in pristine Glucose. To start using Sugar Network related improvements in Shell UI, go to ''Sweets Distribution'' component in Control Panel and enable integration checkbox and restart Sugar. After restarting, Sugar Network client will be available from activities tray and by {{Code|F8}} shortkey.
+
By default, Sugar Shell looks the same as in pristine Glucose. To start using Sugar Network related improvements in the Shell UI, go to the ''Sweets Distribution'' component in the Control Panel, enable the integration checkbox, and restart Sugar. After restarting, the Sugar Network client will be available from the Activities tray and the {{Code|F8}} shortcut key.
  
 
== Deployment oriented ==
 
== Deployment oriented ==
  
The following features are being targeted to Sugar distributors who create downstream solutions based on Sweets Distribution and experienced users who enable these features on their own risk.
+
The following features are being targeted for Sugar distributors who create downstream solutions based on Sweets Distribution and experienced users who enable these features at their own risk.
  
 
* [[Platform_Team/Sweets_Distribution/Features/Blacklists|Blacklist Shell components]]<br>Blacklist usage of particular Sugar Shell components.
 
* [[Platform_Team/Sweets_Distribution/Features/Blacklists|Blacklist Shell components]]<br>Blacklist usage of particular Sugar Shell components.
  
 
* [[Platform_Team/Sweets_Distribution/Features/Plugins|Shell plugins]]<br>Pluggable Sugar Shell code to extend current behavior. Factory repository provides the following plugins:
 
* [[Platform_Team/Sweets_Distribution/Features/Plugins|Shell plugins]]<br>Pluggable Sugar Shell code to extend current behavior. Factory repository provides the following plugins:
** [http://git.sugarlabs.org/desktop/sugar-telepathy-plugin telepathy] from {{Code|sugar-telepathy-plugin}} package<br>Alternative implementation of Neighborhood collaboration in Sugar Shell that is assumed to make Telepathy related code more robust.
+
** [http://git.sugarlabs.org/desktop/sugar-telepathy-plugin telepathy] from {{Code|sugar-telepathy-plugin}} package<br>Alternative implementation of Neighborhood collaboration in Sugar Shell, which is assumed to make Telepathy related code more robust.
** [http://git.sugarlabs.org/network/shell-plugin sn] from {{Code|sugar-network-plugin}} package<br>Plugin adds [[Sugar Network]] integration to Sugar Shell. It is also working example how to replace original sugar-datastore with new implementation.
+
** [http://git.sugarlabs.org/network/shell-plugin sn] from {{Code|sugar-network-plugin}} package<br>Plugin adds [[Sugar Network]] integration to the Sugar Shell. It is also a working example how to replace the original sugar-datastore with a new implementation.
** [http://git.sugarlabs.org/server/client client] from {{Code|sugar-client}} package<br>Plugin to initiate various [[Platform_Team/Server_Kit/sugar-client|deployment related routines]] on end user side.
+
** [http://git.sugarlabs.org/server/client client] from the {{Code|sugar-client}} package<br>Plugin to initiate various [[Platform_Team/Server_Kit/sugar-client|deployment related routines]] on the end user system.
** [http://git.sugarlabs.org/desktop/sugar-proxy-plugin proxy] from {{Code|sugar-proxy-plugin}} package<br>Internet proxy configuration.
+
** [http://git.sugarlabs.org/desktop/sugar-proxy-plugin proxy] from the {{Code|sugar-proxy-plugin}} package<br>Internet proxy configuration.
  
 
* Closer integration with login managers<br>Sugar Shell will reuse language setting from GDM manager, [http://bugs.sugarlabs.org/ticket/2603 #2603].
 
* Closer integration with login managers<br>Sugar Shell will reuse language setting from GDM manager, [http://bugs.sugarlabs.org/ticket/2603 #2603].
Line 23: Line 23:
 
=== Default configuration changes ===
 
=== Default configuration changes ===
  
The following changes were made in default Sugar Shell configuration.
+
The following changes were made in the default Sugar Shell configuration.
  
* Registration on school servers is disabled by default<br>Sugar Shell support registration on OLPC XS school server. Sweets Distribution does not provide OLPS XS and this functionality is disabled by default. To revert original behavior, set {{Code|/desktop/sugar/show_register}} GConf key to {{Code|true}}.
+
* Registration on school servers is disabled by default<br>Sugar Shell support registration on OLPC XS school server. Sweets Distribution does not provide OLPS XS, and this functionality is disabled by default. To revert to the original behavior, set the {{Code|/desktop/sugar/show_register}} GConf key to {{Code|true}}.
  
* On initial start, Sugar Shell will ask for user nickname. To revert original behavior (when Shell reuses system user name), set {{Code|/desktop/sugar/user/default_nick}} GConf key to {{Code|system}}.
+
* On initial start, Sugar Shell will ask for a user nickname. To revert to the original behavior (when Shell reuses the system user name), set the {{Code|/desktop/sugar/user/default_nick}} GConf key to {{Code|system}}.

Revision as of 21:04, 18 August 2012

Users oriented

The following features are oriented to end users.

Sugar Network integration

By default, Sugar Shell looks the same as in pristine Glucose. To start using Sugar Network related improvements in the Shell UI, go to the Sweets Distribution component in the Control Panel, enable the integration checkbox, and restart Sugar. After restarting, the Sugar Network client will be available from the Activities tray and the F8 shortcut key.

Deployment oriented

The following features are being targeted for Sugar distributors who create downstream solutions based on Sweets Distribution and experienced users who enable these features at their own risk.

  • Shell plugins
    Pluggable Sugar Shell code to extend current behavior. Factory repository provides the following plugins:
    • telepathy from sugar-telepathy-plugin package
      Alternative implementation of Neighborhood collaboration in Sugar Shell, which is assumed to make Telepathy related code more robust.
    • sn from sugar-network-plugin package
      Plugin adds Sugar Network integration to the Sugar Shell. It is also a working example how to replace the original sugar-datastore with a new implementation.
    • client from the sugar-client package
      Plugin to initiate various deployment related routines on the end user system.
    • proxy from the sugar-proxy-plugin package
      Internet proxy configuration.
  • Closer integration with login managers
    Sugar Shell will reuse language setting from GDM manager, #2603.

Default configuration changes

The following changes were made in the default Sugar Shell configuration.

  • Registration on school servers is disabled by default
    Sugar Shell support registration on OLPC XS school server. Sweets Distribution does not provide OLPS XS, and this functionality is disabled by default. To revert to the original behavior, set the /desktop/sugar/show_register GConf key to true.
  • On initial start, Sugar Shell will ask for a user nickname. To revert to the original behavior (when Shell reuses the system user name), set the /desktop/sugar/user/default_nick GConf key to system.