Sugar Labs - User contributions [en]

Sugar Labs/Getting Involved

2013-10-20T20:03:24Z

Erikos: /* Developer */

<noinclude>{{Translations | [[Sugar_Labs/Getting_Involved|english]] | [[Sugar_Labs/Getting_Involved/lang-es|español]]}}{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude>
__NOTOC__
= Join Sugar Labs =

Apply for membership [[Sugar_Labs/Members|here]].

----

'''We need your help in improving how computers are used in education'''. ''You'' can take an active hand in making Sugar realize its [[Archive/Current_Events/2009-03-17#What_are_our_objectives.3F | '''vision''']]. Making [[What is Sugar?|'''Sugar''']] depends on volunteers who love to engage in authentic activities—activities that help fulfill the potentials they individually see in Sugar's vision. What do you want to see happen? What roles could you fill? Click the role of your choice in the grid below, and then, after selecting a Team or project link, follow the '''Join''' links at the top of the Team or project page (in the green or yellow linkbar) to learn how you can '''Join In'''. We depend on ''you'' getting involved!
<div class="noborder">
{| class="wikitable" cellspacing="0" cellpadding="5" width=100% style="background:#eeeeff;border:5px solid white;text-align:center;"
|-
|valign="TOP" width=33% style="border:5px solid white;"|[[File:Join_Educator.png|link=#Educator]]

[[#Educator | Educator]]

|valign="TOP" width=33% style="border:5px solid white;" |[[File:Join_ContentDeveloper.png|link=#Content Writer]]

[[#Content_Writer | Content Writer]]

|valign="TOP" width=33% style="border:5px solid white;"|[[File:Join_PeoplePerson.png|link=#People Person]]

[[#People_Person | People Person]]
|-
|valign="TOP" width=33% style="border:5px solid white;"|[[File:Join_Developer.png|link=#Developer]]

[[#Developer | Developer]]

|valign="TOP" width=33% style="border:5px solid white;"|[[File:Join_Designer.png|link=#Designer]]

[[#Designer | Designer]]

|valign="TOP" width=33% style="border:5px solid white;"|[[File:Join_Translator.png|link=#Translator]]

[[#Translator | Translator]]
|-
|valign="TOP" colspan="3" style="border:5px solid white;"|
'''[[What could I do in an hour?]]'''
|-
|valign="TOP" colspan="3" style="border:5px solid white;"|
'''[[Ideas for Projects]]'''
|-
|valign="TOP" colspan="3" style="border:5px solid white;"|
Financial contributions are discussed on the [[Sugar Labs/Donate]] page.
|}
</div>

====Learn more====

Help us understand and improve the ability for people to contribute and become deeply involved with Sugar.
{{Iframe|See [http://planet.sugarlabs.org Planet Sugar Labs], our blog aggregator |http://planet.sugarlabs.org|900|600|1}}
* Sugar Labs [[Sugar Labs/Communication channels|Communication channels]], [[:Category:Participate |Participation pages]], [[Sugar Labs/Volunteer Funnel|Volunteer Funnel]], & [[Vacancies]],
* The One Laptop per Child [[olpc:Participate | Participation page]].
<div style="background-color:#a0ff93; border:1px solid #cdf; padding:6px 14px;">
The Sugar community is made of individuals, teams, and relationships.

We all share one thing in common: '''We want to improve how computers are used in education'''.

Join us in discussing the project on the [http://lists.sugarlabs.org/listinfo/iaep It's an Education Project] mailing list. [http://wiki.sugarlabs.org/index.php?title=Special:OpenIDLogin&returnto=Special:UserLogin Open a wiki account here] and edit this site.
</div>

{{Anchor | Educator}}

== Educator ==
[[Image:Join_Educator_BW.png|link=]]

'''Description of this role:''' Focus on Sugar's educational needs. If you are an educator and you would like to contribute to the Sugar project please contact cmeeks at sugarlabs dot org.

'''Skills you possess or want to learn''':
* Explaining complex ideas well, people skills, teaching through digital media, understanding of educational theories and obstacles, paedagogy, ability to communicate with and influence developers.

'''Teams/projects associated with this role''':
* | [[Education Team]] | [[Activity Team]] | [[Deployment Team]] | [[Local Labs]] |
* | [[Math4Team]] | [[Sugar on a Stick]] | [[Replacing Textbooks]]

'''Tasks typical in this role''':
* Tasks typical in this role: Lesson plans, teacher guides, text book templates/samples, articles, leverage Sugar as an ideal platform for learning, provide guidance and feedback to those working on technical aspects of Sugar, setting educational goals, educational activities.

'''Real person to help you get started''':
* If you are an educator who would like to help with Sugar, please contact walter at sugarlabs dot org.

{{Anchor|ContentWriter}}

== Content Writer ==
[[Image:Join_ContentDeveloper_BW.png|link=]]

'''Description of this role:''' Communicate through words.

'''Skills you possess or want to learn''':
* Writing, editing, grammar, wordsmithing, proof-reading, explaining complex ideas well, teaching, wiki markup, technical knowledge (specific and general).
'''Teams associated with this role''':
* | [[Documentation Team]] | [[Marketing Team]] | [[Wiki Team]] | [[Deployment Team]] | [[Local Labs]] |
* | [[Math4Team]] | [[Replacing Textbooks]]
'''Tasks typical in this role''':
* Write, edit, illustrate, or program an Open Education Resource on any subject for any age in the Sugar Labs [[Replace Textbooks]] project.
* Write a [http://booki.flossmanuals.net FLOSS Manual] for your favorite activity, guides, how-tos, FAQs, knowledge base, lesson plans, teacher guides, text book templates/samples, articles, marketing material, process/methodology documents, editing, release notes.
'''Real person to help you get started''':
* If you are a content writer who would like to help with Sugar, please contact [mailto:mokurai@sugarlabs.org Mokurai].

{{Anchor|PeoplePerson}}

== People Person ==
[[Image:Join_PeoplePerson_BW.png|link=]]

'''Description of this role:''' Communicate through one-on-one contact.

'''Skills you possess or want to learn''':
* People skills, public relations, event organization, customer service/support, enthusiasm.

'''Teams/projects associated with this role''':
* | [[Marketing Team]] | [[Documentation Team]] | [[Deployment Team]] | [[Local Labs]] |
* | [[Sugar on a Stick]] |

'''Tasks typical in this role''':
* Conferences, press releases, local events, organizing events, community management, Sugar Labs forum/IRC help/support tech, send out media/spread Sugar, encourage others to participate, cat herding.

'''Real person to help you get started''':
* If you are a people person who would like to help with Sugar, please contact bernie at sugarlabs dot org.

{{Anchor|Developer}}

== Developer ==
[[Image:Join_Developer_BW.png|link=]]

'''Description of this role:''' Communicate through code.

'''Skills you possess or want to learn''':
* Python, C, GTK+, git, packaging, bug filing, tracking and testing, JavaScript, web app development, GNU/Linux system administration

'''Teams/projects associated with this role''':
* | [[Development Team]] | [[Activity Team]] | [[Platform Team]] | [[BugSquad|Testing Team]] | [[Infrastructure Team]] |
* | [[Summer of Code | Google Summer of Code]] | [[Math4Team]] | [[Development Team/Project Ideas | Project Ideas]] | [[Sugar on a Stick]] |

'''Tasks typical in this role''':
* Get the source code, test & break Sugar, design & build Sugar, file bugs, fix bugs, build packages, develop new features, test, design, develop & help maintain activities, toolchain, scripts.

'''Real person to help you get started''':
* If you are a developer who would like to help with Sugar, please introduce yourself at the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar devel mailing list] or get in touch with Gonzalo via '''gonzalo''' at '''laptop''' dot '''org''' (Activity Team lead).

{{Anchor|Designer}}

== Designer ==
[[Image:Join_Designer_BW.png|link=]]

'''Description of this role:''' Communicate through images.

'''Skills you possess or want to learn''':
* Inkscape, GIMP, other vector & raster graphics tools, OpenOffice, design, usability/interaction.

'''Teams/projects associated with this role''':
* | [[Design Team|Design Team]] | [[Marketing Team]] | [[Documentation Team]] |
* | [[Math4Team]] |

'''Tasks typical in this role''':
* Sugar art work (SVG activity icons, toolbar icons), Activity image content, user interface design, publication design, web design, icons, design mock-ups, conference banners/flyers, logos, materials (t-shirts, CD covers, etc.)

'''Real person to help you get started''':
* If you are a designer who would like to help with Sugar, please contact garycmartin at sugarlabs dot org.

== Translator ==
[[Image:Join_Translator_BW.png|link=]]

'''Description of this role:''' Communicate through interpretation.

'''Skills you possess or want to learn''':
* English, Non-English native language, technical knowledge, Pootle, PO, translation.

'''Teams/projects associated with this role''':
* | [[Translation Team]] | [[Documentation Team]] | [[Wiki Team | Wiki Team]] | [[Local Labs]] | [[Replacing Textbooks]]
'''Tasks typical in this role''':
* Activity and Sugar user interface string translation, localization (l10n), internationalizaton (i18n), marketing materials, documents, OERs, websites, providing cultural specific feedback to other teams.
* If you are a translator who would like to help with Sugar, please contact [mailto:mokurai@sugarlabs.org Mokurai] or [mailto:cjl@sugarlabs.org cjl].

[[Category:Participate]]

Features/Policy

2013-03-27T09:31:34Z

Erikos: /* Propose a feature for addition into the release cycle */

<noinclude>[[Category:Policy]]
[[Category:Feature|.Policy]]
</noinclude>

== Why does this process matter or why should I care? ==
The main goal of the feature policy is to make systematic and predictable the process by which community ideas on how Sugar should evolve get transformed into actionable proposals. These ideas (new features) can be requests from the field or individual propositions on how to enhance the Sugar learning platform.

Furthermore this process describes the steps a Feature owner needs to fulfill to propose the Feature to be part of a Sucrose release cycle and to include it in a Sucrose release.

We are currently in discussing on how this process can be used by activities, too. As Activities are not part of Sucrose (the Sugar platform), they do not need to follow the release cycle. Stay tuned on updates to the Feature process regarding activities.

'''Note:''' For more background on FOSS project development, please refer to Karl Fogel's [http://producingoss.com/ Producing Open Source Software]

=== Who is responsible for this process? ===
The person responsible for managing the Feature Process is our community-designated Release Manager. (The current Release Manager is [http://wiki.sugarlabs.org/go/User:Erikos Simon Schampijer].)

==== Roles ====

In addition to the Release Manager, there are five other distinct roles in the new-feature process: the proposer of the idea; the developer of the idea; the maintainer of the relevant module, the design team and the Sugar community.

* the proposer (or "owner") of the idea is the one that proposes the feature and completes the new feature proposal as described below. The owner may want to follow the development and provide feedback throughout the process;
* the developer of the idea is the one that implements the idea and follows the process to inclusion in a release;
* the maintainer of the module is the one that reviews any code that needs to be merged for a feature;
* the design team is responsible for ensuring the overall consistency and quality of the Sugar experience; They will provide feedback during the process; and
* the community provides feedback throughout the process, but especially at the stage where by we decide which new-feature proposals to pursue.

As noted above, the Release Manager is the one that sets and enforce the policy for features, including setting dates, formalizing processes, etc.

== What is a feature? ==
A feature is defined as a significant change or enhancement to the version of Sugar currently under development that may or may not include new packages. Bugs are not features. We use the bug tracker to report and monitor bugs.

Sugar features are usually considered to meet one or more of the following objectives:

# Highly user-visible changes (beyond artwork or bug fixes)
# Improvements or changes that require non-trivial cross-package integration
# Exciting new capabilities we can trumpet Sugar having—some of this is good public relations. Some examples might include:
#* Adding of new functionality to the Sugar platform, for example: version support in the datastore; file-sharing; etc.
#* Work Sugar contributors are doing upstream as part of their work for Sugar
#* New features from upstream that we are making available in Sugar for the first time
# Significant enough that if not completed properly or without a proper backup plan could delay the release
# Noteworthy enough to call out in the release notes

Similarly, Activity features meet a similar set of criteria:

# Highly user-visible changes (beyond artwork or theme changes)
# Improvements or changes that require non-trivial cross-package integration
# Exciting new capabilities:
#* Adding of new functionality, for example: support for a new ebook format
#* Adding a new activity area, for example: a multimedia editor
#* Better leverage of the Sugar platform, for example: Journal integration for Scratch
# Noteworthy enough to call out in the release notes

It's sometimes easy to mistake new packages, or enhancements, for features. Features have a very specific definition, but here are some questions to ask yourself before engaging the feature process.

# Is this change very visible to end users?
#* In this case "end user" means "someone in the audience for this change", which could be Sugar users, developers, or system administrators.
# Does this change require intervention?
#* This might be a configuration-file format change, or something else that will perturb unsuspecting end users.
#* A change that requires a very simple intervention to revert behavior is not necessarily a feature.
# Is this something that will interest the lay press?
#* The lay press in this case includes Education-oriented sites.

== Starting the process ==
Before starting the process you should have read the feature definition from above and made sure the idea you want to propose does fit into one of the categories. Subsequently, there are three steps needed to go from your original idea to a feature present in a stable release of Sugar:

# Propose a feature to the community;
# Find/name an owner and propose the feature for addition into the release cycle or activity development cycle; and, in the case of platform features,
# Finish the feature by the ''Feature Freeze'' such that it is included in the release.

=== Propose a feature ===
Community members are encouraged to create new pages for features that enhance or improve Sugar. Anyone can propose new features for Sugar, even if you cannot build it yourself. Of course, every feature needs an owner to work on it during the release cycle. If the community agrees on the need for the feature, we will try to find resources to work on it. For proposing a feature you need to:

# Copy the markup from the [[Features/Feature Template]]
#* [{{fullurl:Features/Feature_Template|action=edit}} Click here to load it]
#* Select all the markup and copy
# Add a new wiki subpage named [[Features]]/''Your feature name'' and paste the template markup into it.
# Add details for each of the sections required in the [[Features/Feature_Template | Template]].
#* The template adds <code><nowiki>[[Category:Feature Page Incomplete]]</nowiki></code> to the wiki page. This means that it is not part of the release cycle. See below on how to request inclusion.
# Put a watch on your page by clicking the watch link so you can see changes other people make to your page.
#* '''Note:''' You must be logged in to do this.

'''Note:''' Feature pages do not have to be complete as they are useful for brainstorming and for describing work in process.

If you cannot work on the feature yourself and are looking for other people that might be interested, you should mail the sugar-devel mailing list and discuss it there. The feature page described above should be filled out as completely as possible though to have a base for subsequent discussion.

=== Propose a feature for addition into the release cycle ===
The final goal is to have a feature present in a stable release. There are three major steps needed on which the Release Manager bases his decision to accept a feature or not:

# Owner: The Feature must have a clear owner (The proposer of the feature and the owner can be the same person).
# Community consensus: There should be more YES than NO in the community for this Feature.
#* Send an email to sugar-devel mailing list with [FEATURE] tag in the subject asking for feedback. This is to give the community (deployments, developers, teachers etc) the chance to comment.
#* If your feature adds UI or changes the current UI please add as well the [DESIGN] tag to the subject. Please add the flag as well if the work flow does change or new ones are added. The Design Team should be involved in the discussion to guarantee a consistent design and a consistent work flow in Sugar. When presenting the feature to the release manager the design does not have to be fully completed but the discussion should have been started.
# Documentation: In order to be considered an official feature accepted for the next Sugar release, the feature should be formally documented on a separate wiki page. The wiki page is the same page than the one from above (a blank template is available at [[Features/Feature Template]]). Please make sure it includes the following information.
#* Summary of the feature
#* A designated owner with a link to Sugar home page. The owner is responsible for:
#** making sure the feature is completed according to the schedule
#** communicating periodic status
#** attending feature status meetings
#* Current status
#** last updated
#** estimated percentage of completion
#* Description of the new feature
#* Detailed explanation of what the new feature will do and how it will be implemented
#* Benefit to Sugar
#* Scope
#* How To Test
#* Dependencies--on other packages or features
#* Contingency plan
#* Link to documentation
#* Important information for release notes
#* Put a ''watch'' on your page so you are notified when its category changes. You must be logged in, then click the ''watch'' link at the top of the page.

Once the feature owner believes that the feature is ready for presentation to the Release Manager for ''acceptance'' move your feature from [[:Category:Feature Page Incomplete]] to [[:Category:Feature Ready for Release Manager]]. The Release Manager will then do the sanity check.

=== Acceptance of a feature ===
Acceptance by the Release Manger is a sanity check, presumed in most cases to be a formality, to ensure that new features compliment Sugar guidelines and is manageable, prior to publicizing as officially targeted for the next release.

Feature acceptance is agreement by the Release Manager that a particular feature is:
# consistent with the goals and policies of Sugar
# supported by the Sugar community
# suitable for listing as an Official Feature of the next release of Sugar
# important to track prior to feature freeze and could affect timeliness of the release

The Release Manager does not comment on the actual code. Merging of the Feature code is in agreement with the module maintainer following the Sugar [[Development_Team/Code_guidelines | coding guidelines]] and the [[Development_Team/Code_Review | review process]]. The feature itself must not be completed to be accepted by the Release Manager.

If the Feature is accepted the Release Manager moves the Feature to Feature Accepted <version>, such as, [[:Category:Feature Accepted {{Upcoming Stable Release}}]]. If the feature is denied the Release Manager moves the Feature to [[:Category:Feature Page Incomplete]] for rework or future resubmission.

=== Things you should consider when proposing a feature ===

# How does it impact learning?
#* What is the benefit to a learner?
# How usable and useful is this feature to a young learners?
#* The majority of our users are '''12 years old or under''', and have little computing experience. When proposing a new feature you should have your audience in mind.
# How well does this fit into a classroom environment?
#* Of course, Sugar is also designed for use outside of the classroom, but those features that can really enhance the classroom experience are key to increasing the adoption of Sugar.
# Don't forget the current user base.
#* Keep in mind that Sugar has already a large user base (1.000.000 learners). There shouldn't be additions or rewrites for the sake of it. This does not mean that the platform stands still and we only do stabilizing work. Good practice is for example to backup your proposal by requests from the field, if possible.
# Does it scale in deployments?
#* Anything that involves a setup process of a person touching each computer is not suitable for deployments.
#* Are there technical aspects which might make your feature workable with a set of 10 computers, but useless with a set of 100? 1000? 10000?
# Does it present technicalities to the deployer?
#* If so, you may be excluding them from using this feature. Unfortunately, many deployments are limited in terms of their technical capabilities, especially when dealing with Linux/open source technologies.
#* If you ''can'' document a technical process in simple terms on a short wiki page, then it may be a realistic task for deployment teams to undertake. But keep in mind that the reader likely does not understand exactly what they are doing, so it needs to be a copy-paste type process.
# Does it rely on (or use) infrastructure or star-style connectivity?
#* If your feature relies or uses networking to talk to some kind of centralized server, then it's probably going to get overloaded after your feature gains adoption in our large user base.
#* Deployers are likely to disable this part of your feature due to the painfully high latencies and costs of internet connections throughout the developing world.
#* If networking is a core part of your feature then make sure it is replicable, e.g. on the OLPC XS school server. Make sure that this process is fully documented with support channels available. For reasons of cost, latency or simply lack of connectivity, many deployments will replicate the global infrastructure you have set up and use your feature exclusively on a LAN level. If this is too difficult then they simply will not use your feature.
# What does it require?
#* The majority of our users use low-specification computers, so keeping things small and fast will greatly increase the size of your userbase, the support from fellow Sugar developers, and the eventual success of your work.

== During the process ==
=== What do the feature owner need to do over the course of the release cycle? ===
The feature is included in the release cycle and follows the [[Development_Team/Release/Roadmap | Release schedule]].

* Complete the feature: The feature must be feature complete by the ''Feature Freeze''.

* Inclusion: The owner of the feature is responsible that the Feature is present at latest in the release at Feature Freeze. The developer will work with the module maintainer (e.g. Tomeu for Sugar), who is ultimately responsible to review and merge the new feature. Please follow the [[Development_Team/Code_Review|development team guidelines]] to make this happen.

* Feature pages: The feature page should be updated to reflect the current status of the feature. At ''Feature Freeze'': The "How To Test" and "User Experience" section must be completed so that testing of that feature can begin. The section 'Release Notes' must be completed when the writing of the release notes begins.

=== Important dates ===
* New features may be proposed (using the guidelines above) and accepted no later than the ''Feature Acceptance'' milestone. Of course you can still propose a feature for an upcoming release.
* New features must be feature complete or close enough to completion by ''Feature Freeze'' that a majority of its functionality can be suitably tested--the "feature is testable".
* All feature must be present in the release after Feature Freeze.
* After the release at ''Feature Freeze'' all features will be evaluated based on test results to date.
* Possible reversion of a feature is latest at the ''UI Freeze'' release.
* The Release Manager will send individual reminders and announcements to sugar-devel list as necessary
* A summary status for all the features targeted to a particular release will be collected on the [[{{Upcoming Stable Release}}/Feature List]] page which references and briefly explains the feature. The Release Manager will maintain this page.
* Reminders to developers about upcoming feature deadlines will be sent to sugar-devel.
* Nag mail to developers with delinquent feature page updates will be emailed privately and shamed in a nice way on sugar-devel.

=== What is the process for dropping a feature? ===
A feature will be proposed for a vote to be dropped from the ''Accepted Feature'' list by the Release Manager if one of the following occurs:

* Feature is incomplete or not testable at ''Feature Freeze''.
* Feature owner fails to consistently provide status.

Partially completed features can still be listed as ''accepted'' for the upcoming release if the wiki page describing the feature is tailored to reflect the completed work. Dropped features can be proposed again for inclusion in the next release.

0.98/Notes

2013-02-21T15:43:10Z

Erikos: /* API */

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Touch support===
The main feature this cycle was the support for touch screen devices. First of all the icons in the Views that do not have a clear primary action have been changed to reveal the Palette on left click or touch. A good example are the Ad-hoc icons. Since hovering over icons to explore their actions is not possible in a touch screen based UI the decision was to change that behaviour. The same is true for the shared activity icons or the buddy icons in the Neighbourhood and Group View.

===New frame behaviour===
The Frame interaction has been modified, the learner can use three actions to reveal and hide the Frame: move the mouse into one of the corners, use the frame key on the keyboard and a swipe gesture from the top of the screen towards the centre of the the screen.

===New hover feedback in the Views===
While working on the feedback for a long press on the icons in the Views (Home-, Neighbourhood and Group View) we changed the hover feedback to one coherent style in all Views: if you hover over one icon you get a light grey rectangle in the background of the icon indicating the hover over state. When you click or touch the icon it has a dark grey background.

===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

===Search in all Views===
There is now the possibility to search in all the Views, the Home, the Group and the Neighbourhood View.

== What's new for developers ==

===sugar-build replaces sugar-jhbuild===
Thanks to the work from Daniel Narvaez we have a new tool for building Sugar from the sources: [http://shell.sugarlabs.org/~buildbot/docs/index.html sugar-build]. This has replaced our previous tool [http://wiki.sugarlabs.org/go/Development_Team/Jhbuild sugar-jhbuild]. sugar-build does currently support several distributions out of the box Fedora 17, Fedora 18, Ubuntu 12.10, Debian Wheezy in both 32-bit and 64-bit. And adding a new distributions is possible and [http://sugarlabs.org/~dnarvaez/sugar-docs/build.html#adding-a-new-distribution documented] as well. Try it out, you will love the ease and reliability of this new tool.

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3, notably is for example the removal of the deprecated _shared_activity member in the activity base class, collaboration might be broken if you do not port that over.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.3.tar.bz2 sugar 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.3.tar.bz2 sugar-toolkit-gtk3 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.2.tar.bz2 sugar-artwork 0.98.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.1.tar.bz2 sugar-datastore 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2408.tar.gz etoys 5.0.2408]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2013-01-14T11:10:55Z

Erikos: /* sugar-build replaces sugar-jhbuild */

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Touch support===
The main feature this cycle was the support for touch screen devices. First of all the icons in the Views that do not have a clear primary action have been changed to reveal the Palette on left click or touch. A good example are the Ad-hoc icons. Since hovering over icons to explore their actions is not possible in a touch screen based UI the decision was to change that behaviour. The same is true for the shared activity icons or the buddy icons in the Neighbourhood and Group View.

===New frame behaviour===
The Frame interaction has been modified, the learner can use three actions to reveal and hide the Frame: move the mouse into one of the corners, use the frame key on the keyboard and a swipe gesture from the top of the screen towards the centre of the the screen.

===New hover feedback in the Views===
While working on the feedback for a long press on the icons in the Views (Home-, Neighbourhood and Group View) we changed the hover feedback to one coherent style in all Views: if you hover over one icon you get a light grey rectangle in the background of the icon indicating the hover over state. When you click or touch the icon it has a dark grey background.

===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

===Search in all Views===
There is now the possibility to search in all the Views, the Home, the Group and the Neighbourhood View.

== What's new for developers ==

===sugar-build replaces sugar-jhbuild===
Thanks to the work from Daniel Narvaez we have a new tool for building Sugar from the sources: [http://shell.sugarlabs.org/~buildbot/docs/index.html sugar-build]. This has replaced our previous tool [http://wiki.sugarlabs.org/go/Development_Team/Jhbuild sugar-jhbuild]. sugar-build does currently support several distributions out of the box Fedora 17, Fedora 18, Ubuntu 12.10, Debian Wheezy in both 32-bit and 64-bit. And adding a new distributions is possible and [http://sugarlabs.org/~dnarvaez/sugar-docs/build.html#adding-a-new-distribution documented] as well. Try it out, you will love the ease and reliability of this new tool.

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.3.tar.bz2 sugar 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.3.tar.bz2 sugar-toolkit-gtk3 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.2.tar.bz2 sugar-artwork 0.98.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.1.tar.bz2 sugar-datastore 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2408.tar.gz etoys 5.0.2408]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2013-01-11T17:08:28Z

Erikos: /* What is new for users */

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Touch support===
The main feature this cycle was the support for touch screen devices. First of all the icons in the Views that do not have a clear primary action have been changed to reveal the Palette on left click or touch. A good example are the Ad-hoc icons. Since hovering over icons to explore their actions is not possible in a touch screen based UI the decision was to change that behaviour. The same is true for the shared activity icons or the buddy icons in the Neighbourhood and Group View.

===New frame behaviour===
The Frame interaction has been modified, the learner can use three actions to reveal and hide the Frame: move the mouse into one of the corners, use the frame key on the keyboard and a swipe gesture from the top of the screen towards the centre of the the screen.

===New hover feedback in the Views===
While working on the feedback for a long press on the icons in the Views (Home-, Neighbourhood and Group View) we changed the hover feedback to one coherent style in all Views: if you hover over one icon you get a light grey rectangle in the background of the icon indicating the hover over state. When you click or touch the icon it has a dark grey background.

===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

===Search in all Views===
There is now the possibility to search in all the Views, the Home, the Group and the Neighbourhood View.

== What's new for developers ==

===sugar-build replaces sugar-jhbuild===
Thanks to the work from Daniel Narvaez we have a new tool for building Sugar from the sources: [http://sugarlabs.org/~dnarvaez/sugar-docs/index.html sugar-build]. This has replaced our previous tool [http://wiki.sugarlabs.org/go/Development_Team/Jhbuild sugar-jhbuild]. sugar-build does currently support several distributions out of the box Fedora 17, Fedora 18, Ubuntu 12.10, Debian Wheezy in both 32-bit and 64-bit. And adding a new distributions is possible and [http://sugarlabs.org/~dnarvaez/sugar-docs/build.html#adding-a-new-distribution documented] as well. Try it out, you will love the ease and reliability of this new tool.

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.3.tar.bz2 sugar 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.3.tar.bz2 sugar-toolkit-gtk3 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.2.tar.bz2 sugar-artwork 0.98.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.1.tar.bz2 sugar-datastore 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2408.tar.gz etoys 5.0.2408]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2013-01-10T13:52:49Z

Erikos: /* What's new for developers */

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Touch support===
The main feature this cycle was the support for touch screen devices. First of all the icons in the Views that do not have a clear primary action have been changed to reveal the Palette on left click or touch. A good example are the Ad-hoc icons. Since hovering over icons to explore their actions is not possible in a touch screen based UI the decision was to change that behaviour. The same is true for the shared activity icons or the buddy icons in the Neighbourhood and Group View.

===New frame behaviour===
The Frame interaction has been modified, the learner can use three actions to reveal and hide the Frame: move the mouse into one of the corners, use the frame key on the keyboard and a swipe gesture from the top of the screen towards the centre of the the screen.

===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

===Search in all Views===
There is now the possibility to search in all the Views, the Home, the Group and the Neighbourhood View.

== What's new for developers ==

===sugar-build replaces sugar-jhbuild===
Thanks to the work from Daniel Narvaez we have a new tool for building Sugar from the sources: [http://sugarlabs.org/~dnarvaez/sugar-docs/index.html sugar-build]. This has replaced our previous tool [http://wiki.sugarlabs.org/go/Development_Team/Jhbuild sugar-jhbuild]. sugar-build does currently support several distributions out of the box Fedora 17, Fedora 18, Ubuntu 12.10, Debian Wheezy in both 32-bit and 64-bit. And adding a new distributions is possible and [http://sugarlabs.org/~dnarvaez/sugar-docs/build.html#adding-a-new-distribution documented] as well. Try it out, you will love the ease and reliability of this new tool.

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.3.tar.bz2 sugar 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.3.tar.bz2 sugar-toolkit-gtk3 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.2.tar.bz2 sugar-artwork 0.98.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.1.tar.bz2 sugar-datastore 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2408.tar.gz etoys 5.0.2408]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2013-01-07T19:08:42Z

Erikos: /* New frame behaviour */

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Touch support===
The main feature this cycle was the support for touch screen devices. First of all the icons in the Views that do not have a clear primary action have been changed to reveal the Palette on left click or touch. A good example are the Ad-hoc icons. Since hovering over icons to explore their actions is not possible in a touch screen based UI the decision was to change that behaviour. The same is true for the shared activity icons or the buddy icons in the Neighbourhood and Group View.

===New frame behaviour===
The Frame interaction has been modified, the learner can use three actions to reveal and hide the Frame: move the mouse into one of the corners, use the frame key on the keyboard and a swipe gesture from the top of the screen towards the centre of the the screen.

===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

===Search in all Views===
There is now the possibility to search in all the Views, the Home, the Group and the Neighbourhood View.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.3.tar.bz2 sugar 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.3.tar.bz2 sugar-toolkit-gtk3 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.2.tar.bz2 sugar-artwork 0.98.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.1.tar.bz2 sugar-datastore 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2408.tar.gz etoys 5.0.2408]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2013-01-07T19:03:37Z

Erikos: /* What is new for users */

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Touch support===
The main feature this cycle was the support for touch screen devices. First of all the icons in the Views that do not have a clear primary action have been changed to reveal the Palette on left click or touch. A good example are the Ad-hoc icons. Since hovering over icons to explore their actions is not possible in a touch screen based UI the decision was to change that behaviour. The same is true for the shared activity icons or the buddy icons in the Neighbourhood and Group View.

===New frame behaviour===
- toggle frame
- remove hover to hide the Frame
- Gesture to reveal the frame

===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

===Search in all Views===
There is now the possibility to search in all the Views, the Home, the Group and the Neighbourhood View.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.3.tar.bz2 sugar 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.3.tar.bz2 sugar-toolkit-gtk3 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.2.tar.bz2 sugar-artwork 0.98.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.1.tar.bz2 sugar-datastore 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2408.tar.gz etoys 5.0.2408]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2013-01-07T18:15:10Z

Erikos: /* What is new for users */

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

===Search in all Views===
There is now the possibility to search in all the Views, the Home, the Group and the Neighbourhood View.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.3.tar.bz2 sugar 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.3.tar.bz2 sugar-toolkit-gtk3 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.2.tar.bz2 sugar-artwork 0.98.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.1.tar.bz2 sugar-datastore 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2408.tar.gz etoys 5.0.2408]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2013-01-07T18:09:11Z

Erikos: update glucose version numbers

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.3.tar.bz2 sugar 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.3.tar.bz2 sugar-toolkit-gtk3 0.98.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.2.tar.bz2 sugar-artwork 0.98.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.1.tar.bz2 sugar-datastore 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2408.tar.gz etoys 5.0.2408]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

Development Team/Release

2013-01-07T16:54:07Z

Erikos: /* Branching */ new release numbers

<noinclude>{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>
== Goals and modules proposal ==

At the beginning of each release [[:Category:Platform Cycle|cycle]], maintainers will work on a set of goals, document them and assign owners. See the upcoming stable release, [[{{Upcoming Stable Release}}/Roadmap]]. (These goals typically involve major interventions or the addition of new components, e.g., someone develops a speech engine specially for his mother tongue and wants it in Sugar. Hence, the process described below is primarily for module maintainers. If you are a developer with a feature or bug fix, you may want to refer to the [[Features/Policy|new feature process]].)

=== New modules proposal ===

The time period available to make a proposal is indicated on the schedule. To propose a new activity send mail to the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], providing the following information:

(See [[Features/Feature Template]].)

* Short description of the features.
* Screenshots or screencasts.
* Are you willing to follow the [[Development Team/Release/Roadmap#Schedule|Schedule]]?
* Are you willing to provide regular source releases? (releases need to be done as well when there are only changes in translations)
* System components the activity depends on.
* Maintainer and members of the developer team, with links to a User page on the wiki or their homepage on the web.
* Status of internationalization.
* Code repository.
* Bug tracking system.
* Homepage.

Criteria for approval will be:

* Supports internationalisation and localisation.
* Does not duplicate the functionalities of other activities.
* Provide functionality that the community judges as important for reaching the goals of the project.
* Maintainer responsiveness and willingness to provide regular releases.



== Module release ==

For both intermediates and final releases module maintainers are responsible to announce the module release and make the sources available. Note that the release number of the module does not need to match the Sucrose release number.
More in detail:

{{Anchor|Glucose}}
=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> (base) modules===
* Build a source tarball

make distcheck

* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v0.81.9).

* test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there. The preferred location for glucose modules is:
shell.sugarlabs.org:/upload/sources/sucrose/glucose/(module_name)/
which translates to:
http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/

* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.

{{Anchor|Fructose}}
===<abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> (base activity) modules===
* Build a source tarball
If your activity uses bundlebuilder you can use the dist_source command to generate a source tarball. Note, use a clean checkout of the repository - due to how bundlebuilder works at the moment files you would place in the directory e.g. x.patch would be included in the tarball as well.

python setup.py dist_source

The tarball will be generated inside the dist directory.

* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20).

* Test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there.

The preferred location for fructose components is:
shell.sugarlabs.org:/upload/sources/sucrose/fructose/(module_name)/
which translates to:
http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/

* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.

=== Using the release script ===
For both, fructose and glucose components you can use the release script in [http://git.sugarlabs.org/projects/sugar-tools sugar-tools] to do the above tasks in one go.

You can check out the available commands (Note, the script does try to release the software of the directory you are currently in):

./release --help

==== For sucrose activities ====

===== Before release =====

Be sure to have the same state as origin/master, git pull, git log, gitstatus, git reset --hard origin/master

===== Release =====

cd into the activity directory, run the sugar-tools 'release' script from there

~/prog/sugar-tools/release

If you want to be sure about the version you can pass the version you want it to be to the script:

~/prog/sugar-tools/release -v 0.96.5

Requirements:

* has to be done in a sugar shell
* user needs ssh access to sugarlabs.org
* user needs write access to the upload directory: http://download.sugarlabs.org/sources/sucrose/fructose/

===== Upload the .xo file to ASLO =====

Tarball is uploaded but you're not done yet, you need to upload the .xo file to ASLO manually.

== Sugar release cycle==
{{Template:Platform Cycle Linkbar}}

Each release cycle will include development, beta, release candidate and final releases. The release team is responsible to coordinate with module maintainers, pull the updated modules together, perform basic QA and announce it. More in detail:

* Ensure that all the module releases are available by the scheduled date.
* Construct a sugar-jhbuild moduleset out of them. Run automatic and manual QA on it.
* If issues arise coordinate with the relevant module maintainers to solve them.
* Announce the release on sugar-devel@lists.sugarlabs.org, including a reference to the sugar-jhbuild moduleset, references to each source module and a global list of changes.

=== Roadmap Update ===

The Development Team's [[{{Upcoming Stable Release}}/Roadmap|Roadmap]] is updated at the beginning of each release cycle by the release team. It includes:

* Detailed schedule of release dates and freeze points.
* List of modules and external dependencies.
* Reference to all the tickets considered for the release.
* References to the new feature proposals.

=== Feature freeze ===
By Feature Freeze all new features have to be complete, reviewed and pushed to the repository. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.

This allows developers to concentrate on refining the new features instead of adding yet more functionality.

The feature freeze affects all the modules included in the release and comprise also ABI for public libraries. Exceptions might be considered by the release team but they will be extremely rare. To request an exception send mail to [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], referencing the patches you would like to land. It will have to be granted by two [[Development Team/Release/Contacts|members]] of the release team, on the base of community feedback.

=== UI Freeze ===
Major UI revisions or changes must be done before this date.

This encourages developers to focus on stability and bug-fixing rather than UI changes. At this point, documentation writers do not have to worry that their work will become outdated.

If you really need to do an UI change you have to ask an exception from the release team and must notify the documentation team when accepted.

=== String cooling===
String changes have to be announced, but no exceptions have to be requested. As soon as the change is committed in git, notify the [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] about it.

=== String Freeze===
After this date every string change has to be requested and to be approved. Please send an exception to the [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] and [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] if you need to break the string freeze and ask for an exception. The localization team lead and two members of the release team need to approve such a break.

=== Stabilizing ===
In the stabilizing phase we request every bug fix to be tied to a ticket including a testing plan. Please add the testcase in the ticket comment field. You need to mark it with |TestCase|. This adds better readability and our script that pulls together the test cases for each release is able to find it as well. For example:
|TestCase|
Click on Browse, Read, Pippy icons in the homepage and make sure all of them starts correctly.

=== Hard code freeze ===
When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered. To request approval send mail to sugar-devel@lists.sugarlabs.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two [[Development Team/Release/Contacts#People|members]] of the team.

=== Branching ===

After the final release of a module, a branch should be created to host further stable development. Please use a name in the form: sucrose-XXX (for example sucrose-0.84). Each module maintainer is responsible to inform the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] and [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org] lists about the branch.

A new branch is created on the Pootle server, e.g., Fructose-0.96 and Fructose-0.98. The Localization team (the coordinator of a translation team) may push translations to any or all of the corresponding branches of your project. Changes to your master branch are not necessarily intended for the release branches as well.

You can create a remote branch like this (in your repository):

git branch sucrose-0.98
git push origin sucrose-0.98

You can as well branch off at a specific commit:

git checkout -b [commit id] [branch name]
e.g. git checkout -b 1641b9ae0703190df383619202ac33e60c130bb9 sugar-0.96

And to work on it (in your repository):

git checkout -b sucrose-0.98 origin/sucrose-0.98
git pull

== Bug triaging ==

Module maintainers should ensure that their plans for the release are clearly reflected in the bug tracking system. They are responsible to set milestones and priorities accordingly, in cooperation with the release and the QA teams.

Each commit or set of commit should have a ticket associated. The ticket number should be always mentioned in the git log and is used to automatically build the list of module changes for the releases.

== Automation ==

TBD Many of the steps described in this document can be easily automated for maintainers which are using the Sugar Labs infrastructure and for the release team. Though as a first pass we want to get the workflow right, even if it involves more manual step than strictly required.

==Related pages==
{{Template:Platform Cycle Linkbar}}

See also [[:Category:Release Notes]]{{Special:PrefixIndex/{{PAGENAME}}/}}

Development Team/Release/Modules

2013-01-07T10:20:00Z

Erikos: /* Glucose */ Update for Sasha stepping down: http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041377.html

<noinclude>[[Category:Development Team]]
'''See also''' [[:Category:Platform Cycle]].

:'''Bug Tracking''': http://bugs.sugarlabs.org/

:'''Home page''': http://sugarlabs.org/
</noinclude>
== Glucose ==
:(Core modules)

{| class="wikitable"
|-
!Module
!Lead Maintainer
!Co-maintainers
!Code Repository
|-
|sugar
|[[User:Erikos|Simon Schampijer]] [[User:Manuq|Manuel Quiñones]]
|[[User:MartinDengler|Martin Dengler]]
|http://git.sugarlabs.org/projects/sugar
|-
|sugar-datastore
|[[User:Erikos|Simon Schampijer]] [[User:Manuq|Manuel Quiñones]]
|
|http://git.sugarlabs.org/projects/sugar-datastore
|-
|sugar-artwork
|[[User:Erikos|Simon Schampijer]] [[User:Manuq|Manuel Quiñones]]
|[[User:BenjaminBerg|Benjamin Berg]] [[User:Garycmartin|Gary C. Martin]]
|http://git.sugarlabs.org/projects/sugar-artwork
|-
|sugar-toolkit-gtk3
|[[User:Erikos|Simon Schampijer]] [[User:Manuq|Manuel Quiñones]] [[User:DanielDrake|Daniel Drake]] 
|
|http://git.sugarlabs.org/projects/sugar-toolkit-gtk3
|-
|sugar-toolkit (deprecated)
|[[User:Erikos|Simon Schampijer]] [[User:Manuq|Manuel Quiñones]]
|[[User:MartinDengler|Martin Dengler]]
|http://git.sugarlabs.org/projects/sugar-toolkit
|-
|sugar-base (deprecated)
|[[User:Erikos|Simon Schampijer]] [[User:Manuq|Manuel Quiñones]]
|[[User:MartinDengler|Martin Dengler]]
|http://git.sugarlabs.org/projects/sugar-base
|-
|sugar-presence-service (deprecated)
|[[User:Erikos|Simon Schampijer]]
|[[User:Cassidy|Guillaume Desmottes]]
|http://git.sugarlabs.org/projects/sugar-presence-service
|-
|hulahop (deprecated)
|[[User:Erikos|Simon Schampijer]]
|
|http://git.sugarlabs.org/projects/hulahop
|}

== Fructose ==
:(Base activities)
===Chat===
:Lead Maintainer: [[User:Alsroot|Aleksey Lim]]
:Co-maintainers:
:Code Repository: http://git.sugarlabs.org/chat
:Release tarballs: http://download.sugarlabs.org/sources/sucrose/fructose/Chat/
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Chat, [[Activities/Chat]]

===Browse===
:Lead Maintainer: [[User:manuq|Manuel Quiñones]]
:Co-maintainers: [[User:erikos|Simpon Schampijer]]
:Code Repository: http://git.sugarlabs.org/projects/browse
:Release tarballs:
:Bug Tracking: [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Browse bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Browse, [[Activities/Browse]]

===Read===
:Lead Maintainer: [[User:Godiard|Gonzalo Odiard]] (formerly [http://sayamindu.randomink.org/ Sayamindu Dasgupta])
:Co-maintainers: [[User:Erikos|Simon Schampijer]]
:Code Repository: http://git.sugarlabs.org/projects/read
:Release tarballs:
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Read, [[Activities/Read]]

===Calculate===
:Lead Maintainer: [[User:Garycmartin|Gary C. Martin]] (formerly Reinier Heeres)
:Co-maintainers:
:Code Repository: http://git.sugarlabs.org/projects/calculate
:Release tarballs:
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Calculate, [[Activities/Calculate]]

===Log===
:Lead Maintainer: [[User:Godiard|Gonzalo Odiard]]
:Co-maintainers: [http://edsiper.linuxchile.cl Eduardo Silva], [[User:Alsroot|Aleksey Lim]]
:Code Repository: http://git.sugarlabs.org/projects/log
:Release tarballs:http://download.sugarlabs.org/sources/sucrose/fructose/Log/
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Log

===Write===
:Lead Maintainer: [[User:Godiard|Gonzalo Odiard]] (formerly [http://uwog.net/ J.M. Maurer])
:Co-maintainers: [http://msevior.livejournal.com/ Martin Sevior]
:Code Repository: http://git.sugarlabs.org/projects/write
:Release tarballs:
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Write, [[Activities/Write]]

===Terminal===
:Lead Maintainer: [http://git.sugarlabs.org/projects/terminal/repos/mainline/blobs/master/MAINTAINERS MAINTAINERS], [http://sayamindu.randomink.org/ Sayamindu Dasgupta]
:Co-maintainers: [http://edsiper.linuxchile.cl Eduardo Silva], [[User:Wade|Wade Brainerd]]
:Code Repository: http://git.sugarlabs.org/projects/terminal
:Release tarballs:
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Terminal, [[Activities/Terminal]]

===Pippy===
:Lead Maintainer: [http://git.sugarlabs.org/projects/pippy/repos/mainline/blobs/master/MAINTAINERS MAINTAINERS], [[User:m_anish|Anish Mangal]]
:Co-maintainers: [[User:Cjb|Chris Ball]], [http://cscott.net C. Scott Ananian], [[User:Quozl|James Cameron]]
:Code Repository: http://git.sugarlabs.org/projects/pippy
:Release tarballs:
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Pippy, [[Activities/Pippy]]

===Etoys===
:Lead Maintainer: [[User:Bert|Bert Freudenberg]]
:Co-maintainers: Squeakland developers
:Code Repository: http://dev.laptop.org/git/projects/etoys/ and http://etoys.laptop.org/svn/trunk/etoys/
:Release tarballs: http://download.sugarlabs.org/sources/sucrose/glucose/etoys/
:Bug Tracking: http://tracker.squeakland.org/
:Home page: http://www.squeakland.org/

===Etoys-activity===
:Lead Maintainer: [[User:Bert|Bert Freudenberg]]
:Co-maintainers: Squeakland developers
:Code Repository: http://dev.laptop.org/git/projects/etoys/
:Release tarballs: http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/
:Bug Tracking: http://tracker.squeakland.org/
:Home page: http://wiki.laptop.org/go/Etoys, [[Activities/Etoys]]

===Imageviewer===
:Lead Maintainer: [[User:Alsroot|Aleksey Lim]]
:Past Maintainers: [http://sayamindu.randomink.org/ Sayamindu Dasgupta]
:Co-maintainers:
:Code Repository: http://git.sugarlabs.org/imageviewer
:Release tarballs: http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Image Viewer

===Jukebox===
:Lead Maintainer: [[User:Godiard|Gonzalo Odiard]] (formerly [http://kushaldas.in Kushal Das])
:Co-maintainers:
:Code Repository: http://git.sugarlabs.org/projects/jukebox
:Release tarballs:
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]
:Home page: http://wiki.laptop.org/go/Jukebox

===Turtleart===
:Lead Maintainer: [[User:Walter|Walter Bender]]
:Co-maintainers: Raúl Gutiérrez Segalés 
:Code Repository: http://git.sugarlabs.org/projects/turtleart
:Release tarballs: http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/
:Bug Tracking: [http://bugs.sugarlabs.org bugs.sl.o] 
:Home page: [[Activities/Turtle Art]]

0.98/Notes

2012-12-11T14:31:19Z

Erikos: /* Glucose modules */ updated etoys version

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.1.tar.bz2 sugar 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.1.tar.bz2 sugar-toolkit-gtk3 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.1.tar.bz2 sugar-artwork 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.0.tar.bz2 sugar-datastore 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2408.tar.gz etoys 5.0.2408]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2012-12-11T14:30:19Z

Erikos: /* Fructose modules */

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.1.tar.bz2 sugar 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.1.tar.bz2 sugar-toolkit-gtk3 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.1.tar.bz2 sugar-artwork 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.0.tar.bz2 sugar-datastore 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2403.tar.gz etoys 5.0.2403]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-149.tar.bz2 Browse 149]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-53.tar.bz2 Paint 53]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2012-12-11T14:11:49Z

Erikos: /* Glucose modules */ update to latest releases

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.98.1.tar.bz2 sugar 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.98.1.tar.bz2 sugar-toolkit-gtk3 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.98.1.tar.bz2 sugar-artwork 0.98.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.98.0.tar.bz2 sugar-datastore 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.98.0.tar.bz2 sugar-toolkit 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.98.0.tar.bz2 sugar-base 0.98.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2403.tar.gz etoys 5.0.2403]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-147.tar.bz2 Browse 147]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-52.tar.bz2 Paint 52]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Roadmap

2012-12-05T09:36:22Z

Erikos: /* Schedule */

<noinclude>{{TeamHeader|Development Team|home=Development Team Home|roadmap_link={{Upcoming Stable Release}}/Roadmap}}
[[Category:Roadmap]]
</noinclude>

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

== Sucrose Development ==

Sucrose 0.97.x is an unstable development series intended for testing and
development purposes. Sucrose uses odd minor version numbers to indicate
development status, so this unstable 0.97.x series will finally become
the 0.98 stable release.

== Schedule ==
The Sugar 0.97.x schedule is this time a bit behind the upcoming [http://live.gnome.org/ThreePointThree GNOME 3.5.x development cycle].

''Tarball Monday:'' The tarballs for the modules are always due on Mondays.

''Release Wednesday:'' The releases during the cycle will happen on Wednesdays.

Current freezes in place for the 0.97 development cycle.
{| cellpadding="10" cellspacing="0" border="1"
!Freeze
!Status
!Full Freeze Starting on...
|-
|Feature
|style="background:#ff8080; color:black" | Closed
| Sep 24 2012
|-
|API/ABI
|style="background:#ff8080; color:black" | Closed
| Oct 08 2012
|-
|UI
|style="background:#ff8080; color:black" | Closed
| Oct 08 2012
|-
|String
|style="background:#ff8080; color:black" | Closed
| Oct 08 2012
|-
|Code
|style="background:#ff8080; color:black" | Closed
| Oct 22 2012
|}



Full schedule leading to the 0.98 stable release.
{| cellpadding="10" cellspacing="0" border="1"
!Date
!Task
!Notes
|-
|Mar 26 2012
|Sucrose 0.96.0 Stable tarballs due
|
|-
|Mar 28
|Sucrose 0.96.0 Stable Release
| [http://wiki.sugarlabs.org/go/0.96/Notes 0.96 Notes]
|-
|Apr 16
|Sucrose 0.96.1 Stable tarballs due
|
|-
|Apr 18
|Sucrose 0.96.1 Stable Release
|
|-
|Aug 20
|Sucrose 0.97.1 Unstable tarballs due
|style="background:#ff8a8a; color:black" | Feature submission deadline, Features will be evaluated following the [[Features/Policy]].
|
|-
|Aug 22
|Sucrose 0.97.2 Unstable Release
|
|-
|Aug 27
|Sucrose 0.97.2 Unstable tarballs due
|style="background:#ff8a8a; color:black" | [http://wiki.sugarlabs.org/go/Features/Policy#Acceptance_of_a_feature Feature Acceptance] Acceptance of the features following the [[Features/Policy]].
|-
|Aug 29
|Sucrose 0.97.2 Unstable Release
|
|-
|Sep 24
|Sucrose 0.97.3 Unstable tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Feature_freeze | Feature Freeze]]
|-
|Sep 26
|Sucrose 0.97.3
|
|-
|Oct 08
|Sucrose 0.97.4 beta tarballs due
|style="background:#ff8a8a; color:black" | API/ABI Freeze for 0.95.x Developer APIs should be frozen at this point, [[Development_Team/Release#UI_Freeze | UI Freeze]] No UI changes may be made without approval from the release-team, [[Development_Team/Release#String_Freeze | String Freeze]] No string changes may be made without confirmation from the localization team and notification to the release team
|
|-
|Oct 10
|Sucrose 0.97.4 beta release
|
|-
|Oct 22
|Sucrose 0.97.5 rc tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Hard_code_freeze | Hard code freeze]] starts. No source code changes can be made without approval from the release-team. Translation and documentation can continue.
|-
|Oct 24
|Sucrose 0.97.5 rc release
|
|-
|Nov 26
|Sucrose 0.98 Newstable tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Hard_code_freeze | Hard code freeze]] ends, but other freezes remain in effect for the stable branch.
|-
|Nov 26
|Sucrose 0.98 Newstable Release
|style="background:#ff8a8a; color:black" | Final Release!
|-
|Dez 17
|Sucrose 0.98.1 Bugfix Release tarballs due
|
|-
|Dez 17
|Sucrose 0.98.1 Bugfix Release
|
|}

== Other schedules of interest ==
* [http://live.gnome.org/ThreePointFive GNOME 3.5]
* [http://fedoraproject.org/wiki/Releases/18/Schedule Fedora 18]
* [http://wiki.laptop.org/go/13.1.0/Release_plan OLPC 13.1.0]

== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> Development Team/Release/Modules ==

* [[Development Team/Release/Modules#etoys|etoys]]
* [[Development Team/Release/Modules#sugar|sugar]]
* [[Development Team/Release/Modules#sugar-base|sugar-base]]
* [[Development Team/Release/Modules#sugar-datastore|sugar-datastore]]
* [[Development Team/Release/Modules#sugar-presence-service|sugar-presence-service]]
* [[Development Team/Release/Modules#sugar-toolkit|sugar-toolkit]]
* [[Development Team/Release/Modules#sugar-artwork|sugar-artwork]]

== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> Development Team/Release/Modules ==
* [[Development Team/Release/Modules#chat-activity|chat-activity]]
* [[Development Team/Release/Modules#web-activity|web-activity]]
* [[Development Team/Release/Modules#read-activity|read-activity]]
* [[Development Team/Release/Modules#log-activity|log-activity]]
* [[Development Team/Release/Modules#write-activity|write-activity]]
* [[Development Team/Release/Modules#calculate-activity|calculate-activity]]
* [[Development Team/Release/Modules#terminal-activity|terminal-activity]]
* [[Development Team/Release/Modules#pippy-activity|pippy-activity]]
* [[Development Team/Release/Modules#etoys-activity|etoys-activity]]
* [[Development Team/Release/Modules#jukebox-activity|jukebox-activity]]
* [[Development Team/Release/Modules#turtleart-activity|turtleart-activity]]
* [[Development Team/Release/Modules#imageviewer-activity|imageviewer-activity]]

== Glucose Dependencies ==

* [http://telepathy.freedesktop.org/releases/telepathy-glib/ telepathy-glib]
* [http://telepathy.freedesktop.org/releases/telepathy-gabble/ telepathy-gabble]
* [http://telepathy.freedesktop.org/releases/telepathy-salut/ telepathy-salut]
* [http://telepathy.freedesktop.org/releases/telepathy-python/ telepathy-python]
* [http://squeakvm.org/unix/ squeak-vm]

== Fructose Dependencies ==

* pyabiword

0.98/Roadmap

2012-12-05T09:36:06Z

Erikos: /* Schedule */

<noinclude>{{TeamHeader|Development Team|home=Development Team Home|roadmap_link={{Upcoming Stable Release}}/Roadmap}}
[[Category:Roadmap]]
</noinclude>

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

== Sucrose Development ==

Sucrose 0.97.x is an unstable development series intended for testing and
development purposes. Sucrose uses odd minor version numbers to indicate
development status, so this unstable 0.97.x series will finally become
the 0.98 stable release.

== Schedule ==
The Sugar 0.97.x schedule is this time a bit behind the upcoming [http://live.gnome.org/ThreePointThree GNOME 3.5.x development cycle].

''Tarball Monday:'' The tarballs for the modules are always due on Mondays.

''Release Wednesday:'' The releases during the cycle will happen on Wednesdays.

Current freezes in place for the 0.97 development cycle.
{| cellpadding="10" cellspacing="0" border="1"
!Freeze
!Status
!Full Freeze Starting on...
|-
|Feature
|style="background:#ff8080; color:black" | Closed
| Sep 24 2012
|-
|API/ABI
|style="background:#ff8080; color:black" | Closed
| Oct 08 2012
|-
|UI
|style="background:#ff8080; color:black" | Closed
| Oct 08 2012
|-
|String
|style="background:#ff8080; color:black" | Closed
| Oct 08 2012
|-
|Code
|style="background:#ff8080; color:black" | Open
| Oct 22 2012
|}



Full schedule leading to the 0.98 stable release.
{| cellpadding="10" cellspacing="0" border="1"
!Date
!Task
!Notes
|-
|Mar 26 2012
|Sucrose 0.96.0 Stable tarballs due
|
|-
|Mar 28
|Sucrose 0.96.0 Stable Release
| [http://wiki.sugarlabs.org/go/0.96/Notes 0.96 Notes]
|-
|Apr 16
|Sucrose 0.96.1 Stable tarballs due
|
|-
|Apr 18
|Sucrose 0.96.1 Stable Release
|
|-
|Aug 20
|Sucrose 0.97.1 Unstable tarballs due
|style="background:#ff8a8a; color:black" | Feature submission deadline, Features will be evaluated following the [[Features/Policy]].
|
|-
|Aug 22
|Sucrose 0.97.2 Unstable Release
|
|-
|Aug 27
|Sucrose 0.97.2 Unstable tarballs due
|style="background:#ff8a8a; color:black" | [http://wiki.sugarlabs.org/go/Features/Policy#Acceptance_of_a_feature Feature Acceptance] Acceptance of the features following the [[Features/Policy]].
|-
|Aug 29
|Sucrose 0.97.2 Unstable Release
|
|-
|Sep 24
|Sucrose 0.97.3 Unstable tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Feature_freeze | Feature Freeze]]
|-
|Sep 26
|Sucrose 0.97.3
|
|-
|Oct 08
|Sucrose 0.97.4 beta tarballs due
|style="background:#ff8a8a; color:black" | API/ABI Freeze for 0.95.x Developer APIs should be frozen at this point, [[Development_Team/Release#UI_Freeze | UI Freeze]] No UI changes may be made without approval from the release-team, [[Development_Team/Release#String_Freeze | String Freeze]] No string changes may be made without confirmation from the localization team and notification to the release team
|
|-
|Oct 10
|Sucrose 0.97.4 beta release
|
|-
|Oct 22
|Sucrose 0.97.5 rc tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Hard_code_freeze | Hard code freeze]] starts. No source code changes can be made without approval from the release-team. Translation and documentation can continue.
|-
|Oct 24
|Sucrose 0.97.5 rc release
|
|-
|Nov 26
|Sucrose 0.98 Newstable tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Hard_code_freeze | Hard code freeze]] ends, but other freezes remain in effect for the stable branch.
|-
|Nov 26
|Sucrose 0.98 Newstable Release
|style="background:#ff8a8a; color:black" | Final Release!
|-
|Dez 17
|Sucrose 0.98.1 Bugfix Release tarballs due
|
|-
|Dez 17
|Sucrose 0.98.1 Bugfix Release
|
|}

== Other schedules of interest ==
* [http://live.gnome.org/ThreePointFive GNOME 3.5]
* [http://fedoraproject.org/wiki/Releases/18/Schedule Fedora 18]
* [http://wiki.laptop.org/go/13.1.0/Release_plan OLPC 13.1.0]

== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> Development Team/Release/Modules ==

* [[Development Team/Release/Modules#etoys|etoys]]
* [[Development Team/Release/Modules#sugar|sugar]]
* [[Development Team/Release/Modules#sugar-base|sugar-base]]
* [[Development Team/Release/Modules#sugar-datastore|sugar-datastore]]
* [[Development Team/Release/Modules#sugar-presence-service|sugar-presence-service]]
* [[Development Team/Release/Modules#sugar-toolkit|sugar-toolkit]]
* [[Development Team/Release/Modules#sugar-artwork|sugar-artwork]]

== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> Development Team/Release/Modules ==
* [[Development Team/Release/Modules#chat-activity|chat-activity]]
* [[Development Team/Release/Modules#web-activity|web-activity]]
* [[Development Team/Release/Modules#read-activity|read-activity]]
* [[Development Team/Release/Modules#log-activity|log-activity]]
* [[Development Team/Release/Modules#write-activity|write-activity]]
* [[Development Team/Release/Modules#calculate-activity|calculate-activity]]
* [[Development Team/Release/Modules#terminal-activity|terminal-activity]]
* [[Development Team/Release/Modules#pippy-activity|pippy-activity]]
* [[Development Team/Release/Modules#etoys-activity|etoys-activity]]
* [[Development Team/Release/Modules#jukebox-activity|jukebox-activity]]
* [[Development Team/Release/Modules#turtleart-activity|turtleart-activity]]
* [[Development Team/Release/Modules#imageviewer-activity|imageviewer-activity]]

== Glucose Dependencies ==

* [http://telepathy.freedesktop.org/releases/telepathy-glib/ telepathy-glib]
* [http://telepathy.freedesktop.org/releases/telepathy-gabble/ telepathy-gabble]
* [http://telepathy.freedesktop.org/releases/telepathy-salut/ telepathy-salut]
* [http://telepathy.freedesktop.org/releases/telepathy-python/ telepathy-python]
* [http://squeakvm.org/unix/ squeak-vm]

== Fructose Dependencies ==

* pyabiword

0.98/Notes

2012-12-03T13:28:05Z

Erikos: /* Fructose modules */ add latest Chat

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.97.8.tar.bz2 sugar 0.97.8]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.97.7.tar.bz2 sugar-toolkit-gtk3 0.97.7]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.97.7.tar.bz2 sugar-artwork 0.97.7]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.97.1.tar.bz2 sugar-datastore 0.97.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.97.1.tar.bz2 sugar-toolkit 0.97.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.96.0.tar.bz2 sugar-base 0.96.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2403.tar.gz etoys 5.0.2403]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-147.tar.bz2 Browse 147]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-78.tar.bz2 Chat 78]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-52.tar.bz2 Paint 52]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-32.tar.bz2 Log 32]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2012-11-28T10:59:15Z

Erikos: /* Fructose modules */ welcome Paint 52

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.97.8.tar.bz2 sugar 0.97.8]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.97.7.tar.bz2 sugar-toolkit-gtk3 0.97.7]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.97.7.tar.bz2 sugar-artwork 0.97.7]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.97.1.tar.bz2 sugar-datastore 0.97.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.97.1.tar.bz2 sugar-toolkit 0.97.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.96.0.tar.bz2 sugar-base 0.96.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2403.tar.gz etoys 5.0.2403]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-147.tar.bz2 Browse 147]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-77.tar.bz2 Chat 77]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-52.tar.bz2 Paint 52]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-31.tar.bz2 Log 31]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

0.98/Notes

2012-11-28T09:17:50Z

Erikos: /* Fructose modules */ Updated to the latest releases

<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

Sucrose 0.98 Release Notes

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==
===Alphabetical ordering in the Home View===
The icons in the Home View are now ordered alphabetically. This change has been applied to the favourites view and the activities list view.

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
* The RadioTooolButton expects the "icon_name" property instead of the "named_icon". The API of ToolButton, RadioToolButton and ToggleToolButton has been adjusted to override the icon-name property and add an Icon instance with the set_icon_widget method. [http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/fe11a3aa23c0e7fbc3c0c498e147b0a20348cc12 This change] brings consistent behaviour for all those widgets.

Please see as well the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar
* latest [http://cgit.freedesktop.org/libxklavier/log/ libxklavier] is a soft dependency

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.97.8.tar.bz2 sugar 0.97.8]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.97.7.tar.bz2 sugar-toolkit-gtk3 0.97.7]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.97.7.tar.bz2 sugar-artwork 0.97.7]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.97.1.tar.bz2 sugar-datastore 0.97.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.97.1.tar.bz2 sugar-toolkit 0.97.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.96.0.tar.bz2 sugar-base 0.96.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2403.tar.gz etoys 5.0.2403]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-147.tar.bz2 Browse 147]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-106.tar.bz2 Read 106]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-167.tar.bz2 TurtleArt 167]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-51.tar.bz2 Pippy 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-41.tar.bz2 Calculate 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-77.tar.bz2 Chat 77]
* [http://download.sugarlabs.org/sources/honey/Paint/Paint-51.tar.bz2 Paint 51]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-29.tar.bz2 Jukebox 29]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-31.tar.bz2 Log 31]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-54.tar.bz2 ImageViewer 54]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-84.tar.bz2 Write 84]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-41.tar.bz2 Terminal 41]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.

Features/Touch/Testing

2012-11-26T16:19:27Z

Erikos: /* Write an essay about turtles in the Write activity */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken
* modify an existing tile
* play game
* name the game (Activity title)

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab
* open a new tab using the '+' button
* close the new tab

===Write an essay about turtles in the Write activity===
* open the Write activity
* type a headline
* make this text bold and underline it (when the sub-toolbar of the text options pushes down the text should still be visible)
* type some text and make parts of it coloured
* type some text and make parts of it italic
* type some text at the end of the first page
* type some text at the start of the second page.
* close activity
* resume it (make sure the text is the same)
[[File:Write test case.png|320px]]

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

File:Write test case.png

2012-11-26T16:16:51Z

Erikos: This is a screenshot of the Write test case.

This is a screenshot of the Write test case.

Features/Touch/Testing

2012-11-26T16:15:42Z

Erikos: /* Write an essay about turtles in the Write activity */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken
* modify an existing tile
* play game
* name the game (Activity title)

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab
* open a new tab using the '+' button
* close the new tab

===Write an essay about turtles in the Write activity===
* open the Write activity
* type a headline
* make this text bold and underline it (when the sub-toolbar of the text options pushes down the text should still be visible)
* type some text and make parts of it coloured
* type some text and make parts of it italic
* type some text at the end of the first page
* type some text at the start of the second page.
* close activity
* resume it (make sure the text is the same)

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing

2012-11-26T15:57:34Z

Erikos: /* Write an essay about turtles in the Write activity */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken
* modify an existing tile
* play game
* name the game (Activity title)

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab
* open a new tab using the '+' button
* close the new tab

===Write an essay about turtles in the Write activity===
* open the Write activity
* type a headline (make this text bigger)

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing

2012-11-26T13:55:11Z

Erikos: /* Ebook mode */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken
* modify an existing tile
* play game
* name the game (Activity title)

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab
* open a new tab using the '+' button
* close the new tab

===Write an essay about turtles in the Write activity===
-

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Testing/Browse

2012-11-16T08:05:55Z

Erikos:

This page is about testing the Browse activity. A good first test when verifying issues is to compare with Epiphany which uses the same backend as Browse (WebKitGTK). On the XO you can find Epiphany in GNOME.

==Popup windows==
There are wanted and unwanted popup windows. Here are two test cases:
* http://dev.laptop.org/~erikos/wanted.html
* http://dev.laptop.org/~erikos/unwanted.html

==Test individual web sites==
===Wikipedia===
* Page:
* Description:
* Result:

===Google===
* Page:
* Description:
* Result:

===Reading emails using Gmail===
* Page:
* Description:
* Result:

===SugarLabs activities (ASLO)===
* Page:
* Description:
* Result:

===SugarLabs wiki ===
* Page:
* Description:
* Result:

===OLPC wiki ===
* Page:
* Description:
* Result:

===DHL packet tracking===
* Page: http://www.dhl.de/en/paket/kundenservice/sendungsverfolgung.html
* Description: This page does open a new page to show the search result.
* Result:

Testing/Browse

2012-11-16T08:02:36Z

Erikos: /* Test individual web sites */

==Popup windows==
There are wanted and unwanted popup windows. Here are two test cases:
* http://dev.laptop.org/~erikos/wanted.html
* http://dev.laptop.org/~erikos/unwanted.html

==Test individual web sites==
===Wikipedia===
* Page:
* Description:
* Result:

===Google===
* Page:
* Description:
* Result:

===Reading emails using Gmail===
* Page:
* Description:
* Result:

===SugarLabs activities (ASLO)===
* Page:
* Description:
* Result:

===SugarLabs wiki ===
* Page:
* Description:
* Result:

===OLPC wiki ===
* Page:
* Description:
* Result:

===DHL packet tracking===
* Page: http://www.dhl.de/en/paket/kundenservice/sendungsverfolgung.html
* Description: This page does open a new page to show the search result.
* Result:

Testing/Browse

2012-11-16T08:00:13Z

Erikos: Created page with "==Popup windows== There are wanted and unwanted popup windows. Here are two test cases: * http://dev.laptop.org/~erikos/wanted.html * http://dev.laptop.org/~erikos/unwanted.ht..."

==Popup windows==
There are wanted and unwanted popup windows. Here are two test cases:
* http://dev.laptop.org/~erikos/wanted.html
* http://dev.laptop.org/~erikos/unwanted.html

==Test individual web sites==
===Reading emails using Gmail===
* Page:
* Description:
* Result:

===DHL packet tracking===
* Page: http://www.dhl.de/en/paket/kundenservice/sendungsverfolgung.html
* Description: This page does open a new page to show the search result.
* Result:

0.98/Roadmap

2012-11-14T16:58:56Z

Erikos: /* Schedule */

<noinclude>{{TeamHeader|Development Team|home=Development Team Home|roadmap_link={{Upcoming Stable Release}}/Roadmap}}
[[Category:Roadmap]]
</noinclude>

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

== Sucrose Development ==

Sucrose 0.97.x is an unstable development series intended for testing and
development purposes. Sucrose uses odd minor version numbers to indicate
development status, so this unstable 0.97.x series will finally become
the 0.98 stable release.

== Schedule ==
The Sugar 0.97.x schedule is this time a bit behind the upcoming [http://live.gnome.org/ThreePointThree GNOME 3.5.x development cycle].

''Tarball Monday:'' The tarballs for the modules are always due on Mondays.

''Release Wednesday:'' The releases during the cycle will happen on Wednesdays.

Current freezes in place for the 0.97 development cycle.
{| cellpadding="10" cellspacing="0" border="1"
!Freeze
!Status
!Full Freeze Starting on...
|-
|Feature
|style="background:#ff8080; color:black" | Closed
| Sep 24 2012
|-
|API/ABI
|style="background:#ff8080; color:black" | Closed
| Oct 08 2012
|-
|UI
|style="background:#ff8080; color:black" | Closed
| Oct 08 2012
|-
|String
|style="background:#ff8080; color:black" | Closed
| Oct 08 2012
|-
|Code
|style="background:#f6aa08; color:black" | Open
| Oct 22 2012
|}



Full schedule leading to the 0.98 stable release.
{| cellpadding="10" cellspacing="0" border="1"
!Date
!Task
!Notes
|-
|Mar 26 2012
|Sucrose 0.96.0 Stable tarballs due
|
|-
|Mar 28
|Sucrose 0.96.0 Stable Release
| [http://wiki.sugarlabs.org/go/0.96/Notes 0.96 Notes]
|-
|Apr 16
|Sucrose 0.96.1 Stable tarballs due
|
|-
|Apr 18
|Sucrose 0.96.1 Stable Release
|
|-
|Aug 20
|Sucrose 0.97.1 Unstable tarballs due
|style="background:#ff8a8a; color:black" | Feature submission deadline, Features will be evaluated following the [[Features/Policy]].
|
|-
|Aug 22
|Sucrose 0.97.2 Unstable Release
|
|-
|Aug 27
|Sucrose 0.97.2 Unstable tarballs due
|style="background:#ff8a8a; color:black" | [http://wiki.sugarlabs.org/go/Features/Policy#Acceptance_of_a_feature Feature Acceptance] Acceptance of the features following the [[Features/Policy]].
|-
|Aug 29
|Sucrose 0.97.2 Unstable Release
|
|-
|Sep 24
|Sucrose 0.97.3 Unstable tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Feature_freeze | Feature Freeze]]
|-
|Sep 26
|Sucrose 0.97.3
|
|-
|Oct 08
|Sucrose 0.97.4 beta tarballs due
|style="background:#ff8a8a; color:black" | API/ABI Freeze for 0.95.x Developer APIs should be frozen at this point, [[Development_Team/Release#UI_Freeze | UI Freeze]] No UI changes may be made without approval from the release-team, [[Development_Team/Release#String_Freeze | String Freeze]] No string changes may be made without confirmation from the localization team and notification to the release team
|
|-
|Oct 10
|Sucrose 0.97.4 beta release
|
|-
|Oct 22
|Sucrose 0.97.5 rc tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Hard_code_freeze | Hard code freeze]] starts. No source code changes can be made without approval from the release-team. Translation and documentation can continue.
|-
|Oct 24
|Sucrose 0.97.5 rc release
|
|-
|Nov 26
|Sucrose 0.98 Newstable tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Hard_code_freeze | Hard code freeze]] ends, but other freezes remain in effect for the stable branch.
|-
|Nov 26
|Sucrose 0.98 Newstable Release
|style="background:#ff8a8a; color:black" | Final Release!
|-
|Dez 17
|Sucrose 0.98.1 Bugfix Release tarballs due
|
|-
|Dez 17
|Sucrose 0.98.1 Bugfix Release
|
|}

== Other schedules of interest ==
* [http://live.gnome.org/ThreePointFive GNOME 3.5]
* [http://fedoraproject.org/wiki/Releases/18/Schedule Fedora 18]
* [http://wiki.laptop.org/go/13.1.0/Release_plan OLPC 13.1.0]

== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> Development Team/Release/Modules ==

* [[Development Team/Release/Modules#etoys|etoys]]
* [[Development Team/Release/Modules#sugar|sugar]]
* [[Development Team/Release/Modules#sugar-base|sugar-base]]
* [[Development Team/Release/Modules#sugar-datastore|sugar-datastore]]
* [[Development Team/Release/Modules#sugar-presence-service|sugar-presence-service]]
* [[Development Team/Release/Modules#sugar-toolkit|sugar-toolkit]]
* [[Development Team/Release/Modules#sugar-artwork|sugar-artwork]]

== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> Development Team/Release/Modules ==
* [[Development Team/Release/Modules#chat-activity|chat-activity]]
* [[Development Team/Release/Modules#web-activity|web-activity]]
* [[Development Team/Release/Modules#read-activity|read-activity]]
* [[Development Team/Release/Modules#log-activity|log-activity]]
* [[Development Team/Release/Modules#write-activity|write-activity]]
* [[Development Team/Release/Modules#calculate-activity|calculate-activity]]
* [[Development Team/Release/Modules#terminal-activity|terminal-activity]]
* [[Development Team/Release/Modules#pippy-activity|pippy-activity]]
* [[Development Team/Release/Modules#etoys-activity|etoys-activity]]
* [[Development Team/Release/Modules#jukebox-activity|jukebox-activity]]
* [[Development Team/Release/Modules#turtleart-activity|turtleart-activity]]
* [[Development Team/Release/Modules#imageviewer-activity|imageviewer-activity]]

== Glucose Dependencies ==

* [http://telepathy.freedesktop.org/releases/telepathy-glib/ telepathy-glib]
* [http://telepathy.freedesktop.org/releases/telepathy-gabble/ telepathy-gabble]
* [http://telepathy.freedesktop.org/releases/telepathy-salut/ telepathy-salut]
* [http://telepathy.freedesktop.org/releases/telepathy-python/ telepathy-python]
* [http://squeakvm.org/unix/ squeak-vm]

== Fructose Dependencies ==

* pyabiword

0.98/Roadmap

2012-11-14T16:57:54Z

Erikos: /* Schedule */ adjust 0.98.0 and 0.98.1 date

<noinclude>{{TeamHeader|Development Team|home=Development Team Home|roadmap_link={{Upcoming Stable Release}}/Roadmap}}
[[Category:Roadmap]]
</noinclude>

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

== Sucrose Development ==

Sucrose 0.97.x is an unstable development series intended for testing and
development purposes. Sucrose uses odd minor version numbers to indicate
development status, so this unstable 0.97.x series will finally become
the 0.98 stable release.

== Schedule ==
The Sugar 0.97.x schedule is this time a bit behind the upcoming [http://live.gnome.org/ThreePointThree GNOME 3.5.x development cycle].

''Tarball Monday:'' The tarballs for the modules are always due on Mondays.

''Release Wednesday:'' The releases during the cycle will happen on Wednesdays.

Current freezes in place for the 0.97 development cycle.
{| cellpadding="10" cellspacing="0" border="1"
!Freeze
!Status
!Full Freeze Starting on...
|-
|Feature
|style="background:#ff8080; color:black" | Closed
| Sep 24 2012
|-
|API/ABI
|style="background:#f6aa08; color:black" | Open
| Oct 08 2012
|-
|UI
|style="background:#f6aa08; color:black" | Open
| Oct 08 2012
|-
|String
|style="background:#f6aa08; color:black" | Open
| Oct 08 2012
|-
|Code
|style="background:#9cf99c; color:black" | Open
| Oct 22 2012
|}



Full schedule leading to the 0.98 stable release.
{| cellpadding="10" cellspacing="0" border="1"
!Date
!Task
!Notes
|-
|Mar 26 2012
|Sucrose 0.96.0 Stable tarballs due
|
|-
|Mar 28
|Sucrose 0.96.0 Stable Release
| [http://wiki.sugarlabs.org/go/0.96/Notes 0.96 Notes]
|-
|Apr 16
|Sucrose 0.96.1 Stable tarballs due
|
|-
|Apr 18
|Sucrose 0.96.1 Stable Release
|
|-
|Aug 20
|Sucrose 0.97.1 Unstable tarballs due
|style="background:#ff8a8a; color:black" | Feature submission deadline, Features will be evaluated following the [[Features/Policy]].
|
|-
|Aug 22
|Sucrose 0.97.2 Unstable Release
|
|-
|Aug 27
|Sucrose 0.97.2 Unstable tarballs due
|style="background:#ff8a8a; color:black" | [http://wiki.sugarlabs.org/go/Features/Policy#Acceptance_of_a_feature Feature Acceptance] Acceptance of the features following the [[Features/Policy]].
|-
|Aug 29
|Sucrose 0.97.2 Unstable Release
|
|-
|Sep 24
|Sucrose 0.97.3 Unstable tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Feature_freeze | Feature Freeze]]
|-
|Sep 26
|Sucrose 0.97.3
|
|-
|Oct 08
|Sucrose 0.97.4 beta tarballs due
|style="background:#ff8a8a; color:black" | API/ABI Freeze for 0.95.x Developer APIs should be frozen at this point, [[Development_Team/Release#UI_Freeze | UI Freeze]] No UI changes may be made without approval from the release-team, [[Development_Team/Release#String_Freeze | String Freeze]] No string changes may be made without confirmation from the localization team and notification to the release team
|
|-
|Oct 10
|Sucrose 0.97.4 beta release
|
|-
|Oct 22
|Sucrose 0.97.5 rc tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Hard_code_freeze | Hard code freeze]] starts. No source code changes can be made without approval from the release-team. Translation and documentation can continue.
|-
|Oct 24
|Sucrose 0.97.5 rc release
|
|-
|Nov 26
|Sucrose 0.98 Newstable tarballs due
|style="background:#ff8a8a; color:black" | [[Development_Team/Release#Hard_code_freeze | Hard code freeze]] ends, but other freezes remain in effect for the stable branch.
|-
|Nov 26
|Sucrose 0.98 Newstable Release
|style="background:#ff8a8a; color:black" | Final Release!
|-
|Dez 17
|Sucrose 0.98.1 Bugfix Release tarballs due
|
|-
|Dez 17
|Sucrose 0.98.1 Bugfix Release
|
|}

== Other schedules of interest ==
* [http://live.gnome.org/ThreePointFive GNOME 3.5]
* [http://fedoraproject.org/wiki/Releases/18/Schedule Fedora 18]
* [http://wiki.laptop.org/go/13.1.0/Release_plan OLPC 13.1.0]

== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> Development Team/Release/Modules ==

* [[Development Team/Release/Modules#etoys|etoys]]
* [[Development Team/Release/Modules#sugar|sugar]]
* [[Development Team/Release/Modules#sugar-base|sugar-base]]
* [[Development Team/Release/Modules#sugar-datastore|sugar-datastore]]
* [[Development Team/Release/Modules#sugar-presence-service|sugar-presence-service]]
* [[Development Team/Release/Modules#sugar-toolkit|sugar-toolkit]]
* [[Development Team/Release/Modules#sugar-artwork|sugar-artwork]]

== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> Development Team/Release/Modules ==
* [[Development Team/Release/Modules#chat-activity|chat-activity]]
* [[Development Team/Release/Modules#web-activity|web-activity]]
* [[Development Team/Release/Modules#read-activity|read-activity]]
* [[Development Team/Release/Modules#log-activity|log-activity]]
* [[Development Team/Release/Modules#write-activity|write-activity]]
* [[Development Team/Release/Modules#calculate-activity|calculate-activity]]
* [[Development Team/Release/Modules#terminal-activity|terminal-activity]]
* [[Development Team/Release/Modules#pippy-activity|pippy-activity]]
* [[Development Team/Release/Modules#etoys-activity|etoys-activity]]
* [[Development Team/Release/Modules#jukebox-activity|jukebox-activity]]
* [[Development Team/Release/Modules#turtleart-activity|turtleart-activity]]
* [[Development Team/Release/Modules#imageviewer-activity|imageviewer-activity]]

== Glucose Dependencies ==

* [http://telepathy.freedesktop.org/releases/telepathy-glib/ telepathy-glib]
* [http://telepathy.freedesktop.org/releases/telepathy-gabble/ telepathy-gabble]
* [http://telepathy.freedesktop.org/releases/telepathy-salut/ telepathy-salut]
* [http://telepathy.freedesktop.org/releases/telepathy-python/ telepathy-python]
* [http://squeakvm.org/unix/ squeak-vm]

== Fructose Dependencies ==

* pyabiword

Features/Touch/Testing os11

2012-11-12T17:09:42Z

Erikos: /* File a bug in bugs.sugarlabs.org */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record: ''OSK does cover the title entry'' [http://bugs.sugarlabs.org/ticket/4106 #4106]
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken: ''can not scroll in the tiles list because a tile is selected'' [http://bugs.sugarlabs.org/ticket/4099 #4099]
* modify an existing tile
* play game
* name the game (Activity title): ''clearing the title should be easier'' [http://bugs.sugarlabs.org/ticket/4036 #4036]

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details: ''can not type in password'' [http://bugs.sugarlabs.org/ticket/4207 #4207]
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger': ''can not activate search'' [http://bugs.sugarlabs.org/ticket/4186 #4186]
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab
* open a new tab using the '+' button: ''Add tab button is hard to trigger in touch on XO-4''[http://bugs.sugarlabs.org/ticket/4184 #4184] ''Number of tabs'' [http://bugs.sugarlabs.org/ticket/4185 #4185]
* close the new tab: Focus of url entry stays when closing a tab [http://bugs.sugarlabs.org/ticket/4187 #4187]

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring: colouring is not always accurate (grey icon outlines) [http://bugs.sugarlabs.org/ticket/4188 #4188]

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing os11

2012-11-12T12:41:42Z

Erikos: /* Connect to your access point */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record: ''OSK does cover the title entry'' [http://bugs.sugarlabs.org/ticket/4106 #4106]
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken: ''can not scroll in the tiles list because a tile is selected'' [http://bugs.sugarlabs.org/ticket/4099 #4099]
* modify an existing tile
* play game
* name the game (Activity title): ''clearing the title should be easier'' [http://bugs.sugarlabs.org/ticket/4036 #4036]

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger': ''can not activate search'' [http://bugs.sugarlabs.org/ticket/4186 #4186]
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab
* open a new tab using the '+' button: ''Add tab button is hard to trigger in touch on XO-4''[http://bugs.sugarlabs.org/ticket/4184 #4184] ''Number of tabs'' [http://bugs.sugarlabs.org/ticket/4185 #4185]
* close the new tab: Focus of url entry stays when closing a tab [http://bugs.sugarlabs.org/ticket/4187 #4187]

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring: colouring is not always accurate (grey icon outlines) [http://bugs.sugarlabs.org/ticket/4188 #4188]

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing os11

2012-11-12T12:39:50Z

Erikos: /* Browse: read articles in Wikipedia */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record: ''OSK does cover the title entry'' [http://bugs.sugarlabs.org/ticket/4106 #4106]
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken: ''can not scroll in the tiles list because a tile is selected'' [http://bugs.sugarlabs.org/ticket/4099 #4099]
* modify an existing tile
* play game
* name the game (Activity title): ''clearing the title should be easier'' [http://bugs.sugarlabs.org/ticket/4036 #4036]

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger': ''can not activate search'' [http://bugs.sugarlabs.org/ticket/4186 #4186]
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab
* open a new tab using the '+' button: ''Add tab button is hard to trigger in touch on XO-4''[http://bugs.sugarlabs.org/ticket/4184 #4184] ''Number of tabs'' [http://bugs.sugarlabs.org/ticket/4185 #4185]
* close the new tab: Focus of url entry stays when closing a tab [http://bugs.sugarlabs.org/ticket/4187 #4187]

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing

2012-11-12T12:37:20Z

Erikos:

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken
* modify an existing tile
* play game
* name the game (Activity title)

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab
* open a new tab using the '+' button
* close the new tab

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing os11

2012-11-12T12:36:19Z

Erikos: /* Ebook mode */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record: ''OSK does cover the title entry'' [http://bugs.sugarlabs.org/ticket/4106 #4106]
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken: ''can not scroll in the tiles list because a tile is selected'' [http://bugs.sugarlabs.org/ticket/4099 #4099]
* modify an existing tile
* play game
* name the game (Activity title): ''clearing the title should be easier'' [http://bugs.sugarlabs.org/ticket/4036 #4036]

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger': ''can not activate search'' [http://bugs.sugarlabs.org/ticket/4186 #4186]
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing os11

2012-11-12T12:22:52Z

Erikos: /* Create a Memorize game with pictures taken in Record */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record: ''OSK does cover the title entry'' [http://bugs.sugarlabs.org/ticket/4106 #4106]
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken: ''can not scroll in the tiles list because a tile is selected'' [http://bugs.sugarlabs.org/ticket/4099 #4099]
* modify an existing tile
* play game
* name the game (Activity title): ''clearing the title should be easier'' [http://bugs.sugarlabs.org/ticket/4036 #4036]

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing os11

2012-11-12T12:19:20Z

Erikos: Init the os11 touch testing page

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken
* modify an existing tile
* play game
* name the game (Activity title)

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing

2012-11-12T10:56:17Z

Erikos: /* Browse: read articles in Wikipedia */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken
* modify an existing tile
* play game
* name the game (Activity title)

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* switch to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing

2012-11-12T10:55:44Z

Erikos: /* Connect to your access point */

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken
* modify an existing tile
* play game
* name the game (Activity title)

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* swicth to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and (that you are connected to the Internet by loading a page in Browse)
* verify that the wireless device icon in the Frame has the correct status and colouring

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing

2012-11-12T09:01:01Z

Erikos:

==Scrolling==

===Journal===
* go to the Journal
* scroll through the list using your Finger
* look for a specific entry
* resume an entry

===Browse===
* open Browse
* load a page with long text (e.g. Wikipedia "New York City")
* read the page, look for specific information (e.g. "Music")

===Activities list===
* go to the Home View, open the Activity list
* scroll to a specific entry
* start a new instance

==Activity management==

===Start new/resume in Home View===

===Resume/resume with in Journal===

===Start from Journal detail view===

===Stop a running activity===

===Change favourite property of activity===

===Install an activity===

===Delete an activity===

===Add activity metadata===
* title
* description

===Switch between running activities===
* use the frame (gesture to show/hide the Frame)

==Ebook mode==

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record
* name them in the Journal
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken
* modify an existing tile
* play game
* name the game (Activity title)

===Read an ebook===
* switch laptop in ebook mode
* open Browse and search for an ebook (e.g. Project Gutenberg)
* download an ebook
* resume it with Read from the Journal
* use the gestures available to read the book (e.g. tapping at the ends will go to the next page)
* make annotations
* close and resume and check if annotations are still there

===Search in google===
* switch laptop in ebook mode
* open Browse
* do a search in google (e.g. OLPC wiki)
* open the link in a new tab (long press on the link will reveal a Palette like a right click does)

===File a bug in bugs.sugarlabs.org===
* switch laptop in ebook mode
* open Browse
* load bugs.sugarlabs.org
* verify through a search that the bug has not been filed yet
* login with your account details
* fill in the bug specific information
* (file it if a new issue)

===Browse: read articles in Wikipedia===
* switch laptop in ebook mode
* open Browse
* load en/es/de.wikipedia.org
* search for 'tiger'
* open the article tiger in a new tab (long press on the link will reveal a Palette like a right click does)
* swicth to the 'tiger tab'
* open a link like 'cat species' in a new tab
* switch between those open tabs
* close a tab

===Connect to your access point===
* switch laptop in ebook mode
* (go to the Control Panel and reset the credentials in the network section)
* go to the neighbourhood view
* search for the access point you want to connect to
* tap on the icon and choose connect in the Palette that opens
* use the OSK to fill in the credentials in the password dialogue that opens
* verify that the AP icon has the 'connected' state and that you are connected to the Internet by loading a page in Browse

===Rotate the screen===
* switch laptop in ebook mode
* go to home view
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Read
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Browse
* rotate the screen in portrait mode
* rotate the screen in landscape mode
* open Paint
* rotate the screen in portrait mode
* rotate the screen in landscape mode

Features/Touch/Testing

2012-11-12T08:52:44Z

Erikos: /* Ebook mode */

Features/Touch/Testing

2012-11-12T08:50:38Z

Erikos: /* Create a Memorize game with pictures taken in Record */

Features/Touch/Testing

2012-11-12T08:50:17Z

Erikos: /* Browse articles in Wikipedia */

Features/Touch/Testing

2012-11-12T08:49:53Z

Erikos: /* Ebook mode */

Features/Touch/Testing

2012-11-12T08:38:12Z

Erikos: /* Ebook mode */

Features/Touch/Testing

2012-11-12T08:33:42Z

Erikos: /* Ebook mode */

Features/Touch/Testing

2012-11-12T08:29:51Z

Erikos: add test cases for scrolling

Features/Touch/Testing os8

2012-10-26T14:59:52Z

Erikos: /* Create a Memorize game with pictures taken in Record */

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record: ''OSK does cover the title entry'' [http://bugs.sugarlabs.org/ticket/4106 #4106]
* name them in the Journal
 
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken: ''can not scroll in the tiles list because a tile is selected'' [http://bugs.sugarlabs.org/ticket/4099 #4099]
* modify an existing tile
* play game
* name the game (Activity title): ''clearing the title should be easier'' [http://bugs.sugarlabs.org/ticket/4036 #4036]

Features/Touch/Testing os8

2012-10-26T14:55:38Z

Erikos: /* Create a Memorize game with pictures taken in Record */

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record: ''OSK does cover the title entry''
* name them in the Journal
 
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken: ''can not scroll in the tiles list because a tile is selected'' [http://bugs.sugarlabs.org/ticket/4099 #4099]
* modify an existing tile
* play game
* name the game (Activity title): ''clearing the title should be easier'' [http://bugs.sugarlabs.org/ticket/4036 #4036]

Features/Touch/Testing os8

2012-10-26T14:53:43Z

Erikos: /* Create a Memorize game with pictures taken in Record */

===Create a Memorize game with pictures taken in Record===
* switch laptop in ebook mode
* open Record
* take a few pictures
* name them in Record: ''OSK does cover the title entry''
* name them in the Journal
 
* open Memorize
* go to edit mode
* delete the existing tiles
* add new tiles from the pictures taken: ''can not scroll in the tiles list because a tile is selected'' [http://bugs.sugarlabs.org/ticket/4099 #4099]
* modify an existing tile
* play game
* name the game (Activity title): ''there should be an x button to delete the title in one go''