Changes

Jump to navigation Jump to search
50 bytes added ,  14:29, 31 March 2010
added new section for deployers
Line 21: Line 21:     
[[Image:3G_CP.png|thumb|none|800px|The 3G control-panel section]]
 
[[Image:3G_CP.png|thumb|none|800px|The 3G control-panel section]]
  −
=== Update an activity translation independently of the Sugar release process ===
  −
In general the translation process is tightly coupled with the release workflow. In order to get the latest translations for a particular activity, deployments need either to wait for the activity maintainer to provide a new release or to use the language-pack mechanism, which is distribution specific (and at its best an ugly hack). The [[Features/Enhanced_Gettext | Enhanced Gettext Feature]] adds an extra search path for the translation files of Sugar activities. This allows deployments to add and update activity translations independently of the release process. The alternate search path can be configured using [http://projects.gnome.org/gconf/ GConf configuration system].
      
With this feature it should be easier for deployments who rely on a small translator team to accomplish their job since they no longer need to keep pace with the Sugar release cycle. Furthermore, we hope to alleviate activity maintainers from the burden of making a new release whenever a new translation becomes available.
 
With this feature it should be easier for deployments who rely on a small translator team to accomplish their job since they no longer need to keep pace with the Sugar release cycle. Furthermore, we hope to alleviate activity maintainers from the burden of making a new release whenever a new translation becomes available.
Line 31: Line 28:     
[[Image:Activity_fails_to_start.png|thumb|none|800px|Display message when an activity fails to start]]
 
[[Image:Activity_fails_to_start.png|thumb|none|800px|Display message when an activity fails to start]]
  −
=== Customize the Sugar font size ===
  −
This [[Features/Font_configuration | Feature]] adds the possibility for distributors and deployers to customize the Sugar font size. The proposed solution is one similar to the solutions used in other desktop environments like [http://gnome.org/ GNOME] and [http://kde.org KDE]: allow customization of the base font size used across the entire desktop platform. This is another important step to bring Sugar more in-line with the desktop world and distributors like [http://laptop.org OLPC] will be able to select font sizes without ugly hacks. In Sugar 0.90 there will be a new control panel section that users will be able to customize font size to suit their needs, too.
      
=== A refactored, new feature rich Turtle Art ===
 
=== A refactored, new feature rich Turtle Art ===
Line 54: Line 48:  
See [[0.88/TurtleArt|Turtle Art 0.88 Release Notes]] for more details.
 
See [[0.88/TurtleArt|Turtle Art 0.88 Release Notes]] for more details.
   −
==Update to this version ==
+
== What is new for distributors and deployers ==
Please use the instructions for your distribution (SoaS, Fedora, Ubuntu, Debian etc) of choice to upgrade to this release. Note that it may take a while until the release is packaged for each distribution. Please stay tuned for distribution specific announcements and watch out for updates at [[Downloads|Get Sugar]].
+
 
 +
=== Customize the Sugar font size ===
 +
This [[Features/Font_configuration | Feature]] adds the possibility for distributors and deployers to customize the Sugar font size. The proposed solution is one similar to the solutions used in other desktop environments like [http://gnome.org/ GNOME] and [http://kde.org KDE]: allow customization of the base font size used across the entire desktop platform. This is another important step to bring Sugar more in-line with the desktop world and distributors like [http://laptop.org OLPC] will be able to select font sizes without ugly hacks. In Sugar 0.90 there will be a new control panel section that users will be able to customize font size to suit their needs, too.
 +
 
 +
=== Update an activity translation independently of the Sugar release process ===
 +
In general the translation process is tightly coupled with the release workflow. In order to get the latest translations for a particular activity, deployments need either to wait for the activity maintainer to provide a new release or to use the language-pack mechanism, which is distribution specific (and at its best an ugly hack). The [[Features/Enhanced_Gettext | Enhanced Gettext Feature]] adds an extra search path for the translation files of Sugar activities. This allows deployments to add and update activity translations independently of the release process. The alternate search path can be configured using [http://projects.gnome.org/gconf/ GConf configuration system].  
    
== What's new for developers ==
 
== What's new for developers ==
Line 107: Line 106:  
== Compatibility ==
 
== Compatibility ==
 
''possible compatibility issues''
 
''possible compatibility issues''
 +
 +
== Update to this version ==
 +
Please use the instructions for your distribution (SoaS, Fedora, Ubuntu, Debian etc) of choice to upgrade to this release. Note that it may take a while until the release is packaged for each distribution. Please stay tuned for distribution specific announcements and watch out for updates at [[Downloads|Get Sugar]].
    
== Getting the sources ==
 
== Getting the sources ==
Line 127: Line 129:  
== Looking Forward to 0.90 ==
 
== Looking Forward to 0.90 ==
 
Planning of the next release cycle has started at [[0.90/Roadmap]]. One of the most interesting goals is the [[Development_Team/Collaboration_Refactoring | refactoring of Collaboration]] on which Tomeu and the [http://collabora.co.uk/ Collabora team] are working on.
 
Planning of the next release cycle has started at [[0.90/Roadmap]]. One of the most interesting goals is the [[Development_Team/Collaboration_Refactoring | refactoring of Collaboration]] on which Tomeu and the [http://collabora.co.uk/ Collabora team] are working on.
      
== Credits ==
 
== Credits ==
 
Many people contributed to this release indirectly, including testing, documentation, translation, contributing to the Wiki, outreach to education and developer communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible.
 
Many people contributed to this release indirectly, including testing, documentation, translation, contributing to the Wiki, outreach to education and developer communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible.
3,267

edits

Navigation menu