Sugar Labs - User contributions [en]

Documentation Team/Notes/1.0

2013-02-09T19:17:09Z

Francis: Add Browse links

Most part of the Sugar documentation and resources are out-of-date. The idea is to provide Sugar 1.0 with up-to-date documentation.

==Schedule==

{| cellpadding="10" cellspacing="0" border="1"
!Action
!Status
!Date
|-
|'''Join all documentation resources'''
|style="background:#00ff00; color:black" | '''Current'''
| From February 1st 2013 to March 12th 2013
|-
|'''Sugar feature cycle begins''' Time to purpose the ways to write and provide documentation.
|style="background:#00ff00; color:black" | '''Current'''
| Unknown
|-
|'''Writing''' Time to have user guides for Sugar and its core activities.
|Pending
| From March 12th 2013
|-
|-
|style="background:#cccccc; color:black" | Add your point here...
|style="background:#cccccc; color:black" | Unknown
|style="background:#cccccc; color:black" | Unknown
|-
|'''Sugar feature cycle closes''' Deadline to purpose new ideas.
|Coming
| Unknown.
|-
|'''Sugar 1.0 Release Candidate''' Time to update documentation Screenshots.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|-
|'''Sugar 1.0.x bugfixed Release''' All work is released.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|}

==Resources==

There is many documentation, out-of-date and being updated. These are the resources to join and create an only documentaton.

{| cellpadding="10" cellspacing="0" border="1"
!Title
!Status
|-
|[http://en.flossmanuals.net/sugar/ Sugar FLOSS Manual]
|Out of date since 2011
|-
|[http://laptop.org/manual XO Manual] (Sugar chapters)
|Sugar content deprecated
|-
|[http://wiki.laptop.org/go/Help_Activity_refresh/TOC OLPC-SF Summit 2011 Work]
|Not finished. Needs a very short update.
|-
|[http://wiki.laptop.org/go/OLPC_SanFranciscoBayArea/OLPCSF_Community_Summit_2011/Help_Activity_Refresh#Existing_draft_chapters Activity specific chapters]
|Incomplete. Will need a short update near the 1.0 release.
|-
|[[Tutorials|Sugar Tutorials]]
|Up-to-date. dd write to USB SAMPLE.iso of tutorial.pdf's (insert USB and open with write in sugar) http://people.sugarlabs.org/Tgillard/Tutorial.iso 5.3M
|-
|Add your link here
|...
|-
|}

==Components to document==

===Sugar environment===
* Home View (List and favourites)
* Frame
* Control Panel
* Mesh - Neighborhood and group view.
* Journal

===Activities===

Feel free to add a core activity.

* Basics (Opening, closing, saving data in Journal, collaboration, etc.)
* Core activity guides
** Browse
*** [http://laptop.org/8.2.0/manual/Browse_Introduction.html XO Manual] (Very old)
*** [http://wiki.sugarlabs.org/go/Activities/Browse Sugar FLOSS Manual] (Last update: Sugar 0.86)
*** [http://wiki.laptop.org/go/Help_Activity_refresh/Chapter/Browse SF Summit Work] (Sugar 0.94, needs screen-shots with Sugar 1 style)
** Calculate
** Chart
** Chat
** Dimensions
** Etoys (Already documented by Squeakland, low priority)
** Fototoon
** Irc
** Jukebox
** Labyrinth
** Measure
** Memorize
** Paint
** Physics
** Pippy
** Portfolio
** Record
** Read
** Scratch (Already documented, low priority)
** Terminal
** Tam Tam
** Turtle Blocks
** Wikipedia
** Write

== Multimedia content ==

* Mute video/animation purposes
** Add your purpose here

* Videos with audio purposes Research about i18n.
** Add your purpose here.

== Writing format ==

The purpose is about using [http://projectmallard.org/ Mallard] to have i18n support.

== Activity documentation template ==

This template is used in wiki pages and modified to be a user guide provided optionally with each activity.

=== About Portfolio ===
=== Using Portfolio ===
* The Toolbars
* Saving to PDF
=== Learning with Portfolio ===
* Samples of student work
=== Extending Portfolio ===

Documentation Team/Notes/1.0

2013-02-09T00:25:23Z

Francis:

Most part of the Sugar documentation and resources are out-of-date. The idea is to provide Sugar 1.0 with up-to-date documentation.

==Schedule==

{| cellpadding="10" cellspacing="0" border="1"
!Action
!Status
!Date
|-
|'''Join all documentation resources'''
|style="background:#00ff00; color:black" | '''Current'''
| From February 1st 2013 to March 12th 2013
|-
|'''Sugar feature cycle begins''' Time to purpose the ways to write and provide documentation.
|style="background:#00ff00; color:black" | '''Current'''
| Unknown
|-
|'''Writing''' Time to have user guides for Sugar and its core activities.
|Pending
| From March 12th 2013
|-
|-
|style="background:#cccccc; color:black" | Add your point here...
|style="background:#cccccc; color:black" | Unknown
|style="background:#cccccc; color:black" | Unknown
|-
|'''Sugar feature cycle closes''' Deadline to purpose new ideas.
|Coming
| Unknown.
|-
|'''Sugar 1.0 Release Candidate''' Time to update documentation Screenshots.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|-
|'''Sugar 1.0.x bugfixed Release''' All work is released.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|}

==Resources==

There is many documentation, out-of-date and being updated. These are the resources to join and create an only documentaton.

{| cellpadding="10" cellspacing="0" border="1"
!Title
!Status
|-
|[http://en.flossmanuals.net/sugar/ Sugar FLOSS Manual]
|Out of date since 2011
|-
|[http://laptop.org/manual XO Manual] (Sugar chapters)
|Sugar content deprecated
|-
|[http://wiki.laptop.org/go/Help_Activity_refresh/TOC OLPC-SF Summit 2011 Work]
|Not finished. Needs a very short update.
|-
|[http://wiki.laptop.org/go/OLPC_SanFranciscoBayArea/OLPCSF_Community_Summit_2011/Help_Activity_Refresh#Existing_draft_chapters Activity specific chapters]
|Incomplete. Will need a short update near the 1.0 release.
|-
|[[Tutorials|Sugar Tutorials]]
|Up-to-date. ¿Need to update screenshots?
|-
|Add your link here
|...
|-
|}
==Components to document==

===Sugar environment===
* Home View (List and favourites)
* Frame
* Control Panel
* Mesh - Neighborhood and group view.
* Journal

===Activities===

Feel free to add a core activity.

* Basics (Opening, closing, saving data in Journal, collaboration, etc.)
* Core activity guides
** Browse
** Calculate
** Chart
** Chat
** Dimensions
** Etoys (Already documented by Squeakland, low priority)
** Fototoon
** Irc
** Jukebox
** Labyrinth
** Measure
** Memorize
** Paint
** Physics
** Pippy
** Portfolio
** Record
** Read
** Scratch (Already documented, low priority)
** Terminal
** Tam Tam
** Turtle Blocks
** Wikipedia
** Write

== Multimedia content ==

* Mute video/animation purposes
** Add your purpose here

* Videos with audio purposes Research about i18n.
** Add your purpose here.

== Writing format ==

The purpose is about using [http://projectmallard.org/ Mallard] to have i18n support.

== Activity documentation template ==

This template is used in wiki pages and modified to be a user guide provided optionally with each activity.

=== About Portfolio ===
=== Using Portfolio ===
* The Toolbars
* Saving to PDF
=== Learning with Portfolio ===
* Samples of student work
=== Extending Portfolio ===

Documentation Team/Notes/1.0

2013-02-07T22:08:11Z

Francis:

Most part of the Sugar documentation and resources are out-of-date. The idea is to provide Sugar 1.0 with up-to-date documentation.

==Schedule==

{| cellpadding="10" cellspacing="0" border="1"
!Action
!Status
!Date
|-
|'''Join all documentation resources'''
|style="background:#00ff00; color:black" | '''Current'''
| From February 1st 2013 to March 12th 2013
|-
|'''Sugar feature cycle begins''' Time to purpose the ways to write and provide documentation.
|style="background:#00ff00; color:black" | '''Current'''
| Unknown
|-
|'''Writing''' Time to have user guides for Sugar and its core activities.
|Pending
| From March 12th 2013
|-
|-
|style="background:#cccccc; color:black" | Add your point here...
|style="background:#cccccc; color:black" | Unknown
|style="background:#cccccc; color:black" | Unknown
|-
|'''Sugar feature cycle closes''' Deadline to purpose new ideas.
|Coming
| Unknown.
|-
|'''Sugar 1.0 Release Candidate''' Time to update documentation Screenshots.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|-
|'''Sugar 1.0.x bugfixed Release''' All work is released.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|}

==Resources==

There is many documentation, out-of-date and being updated. These are the resources to join and create an only documentaton.

{| cellpadding="10" cellspacing="0" border="1"
!Title
!Status
|-
|[http://en.flossmanuals.net/sugar/ Sugar FLOSS Manual]
|Out of date since 2011
|-
|[http://laptop.org/manual XO Manual] (Sugar chapters)
|Sugar content deprecated
|-
|[http://wiki.laptop.org/go/Help_Activity_refresh/TOC OLPC-SF Summit 2011 Work]
|Not finished. Needs a very short update.
|-
|[http://wiki.laptop.org/go/OLPC_SanFranciscoBayArea/OLPCSF_Community_Summit_2011/Help_Activity_Refresh#Existing_draft_chapters Activity specific chapters]
|Incomplete. Will need a short update near the 1.0 release.
|-
|[[Tutorials|Sugar Tutorials]]
|Up-to-date. ¿Need to update screenshots?
|-
|Add your link here
|...
|-
|}
==Components to document==

===Sugar environment===
* Home View (List and favourites)
* Frame
* Control Panel
* Mesh - Neighborhood and group view.
* Journal

===Activities===

Feel free to add a core activity.

* Basics (Opening, closing, saving data in Journal, collaboration, etc.)
* Core activity guides
** Browse
** Calculate
** Chart
** Chat
** Dimensions
** Etoys (Already documented by Squeakland, low priority)
** Fototoon
** Irc
** Jukebox
** Labyrinth
** Measure
** Memorize
** Paint
** Physics
** Pippy
** Portfolio
** Record
** Read
** Scratch (Already documented, low priority)
** Terminal
** Tam Tam
** Turtle Blocks
** Wikipedia
** Write

Documentation Team/Notes/1.0

2013-02-04T21:01:32Z

Francis:

Most part of the Sugar documentation and resources are out-of-date. The idea is to provide Sugar 1.0 with up-to-date documentation.

==Schedule==

{| cellpadding="10" cellspacing="0" border="1"
!Action
!Status
!Date
|-
|'''Join all documentation resources'''
|style="background:#00ff00; color:black" | '''Current'''
| From February 1st 2013 to March 12th 2013
|-
|'''Sugar feature cycle begins''' Time to purpose the ways to write and provide documentation.
|style="background:#00ff00; color:black" | '''Current'''
| Unknown
|-
|'''Writing''' Time to have user guides for Sugar and its core activities.
|Pending
| From March 12th 2013
|-
|-
|style="background:#cccccc; color:black" | Add your point here...
|style="background:#cccccc; color:black" | Unknown
|style="background:#cccccc; color:black" | Unknown
|-
|'''Sugar feature cycle closes''' Deadline to purpose new ideas.
|Coming
| Unknown.
|-
|'''Sugar 1.0 Release Candidate''' Time to update documentation Screenshots.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|-
|'''Sugar 1.0.x bugfixed Release''' All work is released.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|}

==Resources==

There is many documentation, out-of-date and being updated. These are the resources to join and create an only documentaton.

{| cellpadding="10" cellspacing="0" border="1"
!Title
!Status
|-
|[http://en.flossmanuals.net/sugar/ Sugar FLOSS Manual]
|Out of date since 2011
|-
|[http://laptop.org/manual XO Manual] (Sugar chapters)
|Sugar content deprecated
|-
|[http://wiki.laptop.org/go/Help_Activity_refresh/TOC OLPC-SF Summit 2011 Work]
|Not finished. Needs a very short update.
|-
|[http://wiki.laptop.org/go/OLPC_SanFranciscoBayArea/OLPCSF_Community_Summit_2011/Help_Activity_Refresh#Existing_draft_chapters Activity specific chapters]
|Incomplete. Will need a short update near the 1.0 release.
|-
|Add your link here
|...
|-
|}
==Components to document==

===Sugar environment===
* Home View (List and favourites)
* Frame
* Control Panel
* Mesh - Neighborhood and group view.
* Journal

===Activities===

Feel free to add a core activity.

* Basics (Opening, closing, saving data in Journal, collaboration, etc.)
* Core activity guides
** Browse
** Calculate
** Chart
** Chat
** Dimensions
** Etoys (Already documented by Squeakland, low priority)
** Fototoon
** Irc
** Jukebox
** Labyrinth
** Measure
** Memorize
** Paint
** Physics
** Pippy
** Portfolio
** Record
** Read
** Scratch (Already documented, low priority)
** Terminal
** Tam Tam
** Turtle Blocks
** Wikipedia
** Write

Documentation Team/Notes/1.0

2013-02-04T16:33:38Z

Francis: /* Activities */

Most part of the Sugar documentation and resources are out-of-date. The idea is to provide Sugar 1.0 with up-to-date documentation.

==Schedule==

{| cellpadding="10" cellspacing="0" border="1"
!Action
!Status
!Date
|-
|'''Join all documentation resources''' Time to
|style="background:#00ff00; color:black" | '''Current'''
| From February 1st 2013 to March 12th 2013
|-
|'''Sugar feature cycle begins''' Time to purpose the ways to write and provide documentation.
|style="background:#00ff00; color:black" | '''Current'''
| Unknown
|-
|'''Writing''' Time to have user guides for Sugar and its core activities.
|Pending
| From March 12th 2013
|-
|-
|style="background:#cccccc; color:black" | Add your point here...
|style="background:#cccccc; color:black" | Unknown
|style="background:#cccccc; color:black" | Unknown
|-
|'''Sugar feature cycle closes''' Deadline to purpose new ideas.
|Coming
| Unknown.
|-
|'''Sugar 1.0 Release Candidate''' Time to update documentation Screenshots.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|-
|'''Sugar 1.0.x bugfixed Release''' All work is released.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|}

==Resources==

There is many documentation, out-of-date and being updated. These are the resources to join and create an only documentaton.

{| cellpadding="10" cellspacing="0" border="1"
!Title
!Status
|-
|[http://en.flossmanuals.net/sugar/ Sugar FLOSS Manual]
|Out of date since 2011
|-
|[http://laptop.org/manual XO Manual] (Sugar chapters)
|Sugar content deprecated
|-
|[http://wiki.laptop.org/go/Help_Activity_refresh/TOC OLPC-SF Summit 2011 Work]
|Not finished. Needs a very short update.
|-
|[http://wiki.laptop.org/go/OLPC_SanFranciscoBayArea/OLPCSF_Community_Summit_2011/Help_Activity_Refresh#Existing_draft_chapters Activity specific chapters]
|Incomplete. Will need a short update near the 1.0 release.
|-
|Add your link here
|...
|-
|}
==Components to document==

===Sugar environment===
* Home View (List and favourites)
* Frame
* Control Panel
* Mesh - Neighborhood and group view.
* Journal

===Activities===

Feel free to add a core activity.

* Basics (Opening, closing, saving data in Journal, collaboration, etc.)
* Core activity guides
** Browse
** Calculate
** Chart
** Chat
** Dimensions
** Etoys (Already documented by Squeakland, low priority)
** Fototoon
** Irc
** Jukebox
** Labyrinth
** Measure
** Memorize
** Paint
** Physics
** Pippy
** Portfolio
** Record
** Read
** Scratch (Already documented, low priority)
** Terminal
** Tam Tam
** Turtle Blocks
** Wikipedia
** Write

Documentation Team/Notes/1.0

2013-02-04T16:22:17Z

Francis:

Most part of the Sugar documentation and resources are out-of-date. The idea is to provide Sugar 1.0 with up-to-date documentation.

==Schedule==

{| cellpadding="10" cellspacing="0" border="1"
!Action
!Status
!Date
|-
|'''Join all documentation resources''' Time to
|style="background:#00ff00; color:black" | '''Current'''
| From February 1st 2013 to March 12th 2013
|-
|'''Sugar feature cycle begins''' Time to purpose the ways to write and provide documentation.
|style="background:#00ff00; color:black" | '''Current'''
| Unknown
|-
|'''Writing''' Time to have user guides for Sugar and its core activities.
|Pending
| From March 12th 2013
|-
|-
|style="background:#cccccc; color:black" | Add your point here...
|style="background:#cccccc; color:black" | Unknown
|style="background:#cccccc; color:black" | Unknown
|-
|'''Sugar feature cycle closes''' Deadline to purpose new ideas.
|Coming
| Unknown.
|-
|'''Sugar 1.0 Release Candidate''' Time to update documentation Screenshots.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|-
|'''Sugar 1.0.x bugfixed Release''' All work is released.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|}

==Resources==

There is many documentation, out-of-date and being updated. These are the resources to join and create an only documentaton.

{| cellpadding="10" cellspacing="0" border="1"
!Title
!Status
|-
|[http://en.flossmanuals.net/sugar/ Sugar FLOSS Manual]
|Out of date since 2011
|-
|[http://laptop.org/manual XO Manual] (Sugar chapters)
|Sugar content deprecated
|-
|[http://wiki.laptop.org/go/Help_Activity_refresh/TOC OLPC-SF Summit 2011 Work]
|Not finished. Needs a very short update.
|-
|[http://wiki.laptop.org/go/OLPC_SanFranciscoBayArea/OLPCSF_Community_Summit_2011/Help_Activity_Refresh#Existing_draft_chapters Activity specific chapters]
|Incomplete. Will need a short update near the 1.0 release.
|-
|Add your link here
|...
|-
|}
==Components to document==

===Sugar environment===
* Home View (List and favourites)
* Frame
* Control Panel
* Mesh - Neighborhood and group view.
* Journal

===Activities===

Feel free to add your

* Basics (Opening, closing, saving data in Journal, collaboration, etc.)
* Core activity guides
** Browse
** Calculate
** Chart
** Chat
** Dimensions
** Etoys (Already documented by Squeakland, low priority)
** Fototoon
** Irc
** Jukebox
** Labyrinth
** Measure
** Memorize
** Paint
** Physics
** Pippy
** Portfolio
** Record
** Read
** Scratch (Already documented, low priority)
** Terminal
** Tam Tam
** Turtle Blocks
** Wikipedia
** Write

Documentation Team/Notes/1.0

2013-02-04T15:59:51Z

Francis: /* Schedule */

Most part of the Sugar documentation and resources are out-of-date. The idea is to provide Sugar 1.0 with up-to-date documentation.

=Schedule=

{| cellpadding="10" cellspacing="0" border="1"
!Action
!Status
!Date
|-
|'''Join all documentation resources''' Time to
|style="background:#00ff00; color:black" | '''Current'''
| From February 1st 2013 to March 12th 2013
|-
|'''Sugar feature cycle begins''' Time to purpose the ways to write and provide documentation.
|style="background:#00ff00; color:black" | '''Current'''
| Unknown
|-
|'''Writing''' Time to have user guides for Sugar and its core activities.
|Pending
| From March 12th 2013
|-
|-
|style="background:#cccccc; color:black" | Add your point here...
|style="background:#cccccc; color:black" | Unknown
|style="background:#cccccc; color:black" | Unknown
|-
|'''Sugar feature cycle closes''' Deadline to purpose new ideas.
|Coming
| Unknown.
|-
|'''Sugar 1.0 Release Candidate''' Time to update documentation Screenshots.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|-
|'''Sugar 1.0.x bugfixed Release''' All work is released.
|Coming
| Waiting for Sugar 1.0 Release Schedule
|}

=Resources=

There is many documentation, out-of-date and being updated. These are the resources to join and create an only documentaton.

{| cellpadding="10" cellspacing="0" border="1"
!Title
!Status
|-
|[http://en.flossmanuals.net/sugar/ Sugar FLOSS Manual]
|Out of date since 2011
|-
|[http://laptop.org/manual XO Manual] (Sugar chapters)
|Sugar content deprecated
|-
|[http://wiki.laptop.org/go/Help_Activity_refresh/TOC OLPC-SF Summit 2011 Work]
|Not finished. Needs a very short update.
|-
|[http://wiki.laptop.org/go/OLPC_SanFranciscoBayArea/OLPCSF_Community_Summit_2011/Help_Activity_Refresh#Existing_draft_chapters Activity specific chapters]
|Incomplete. Will need a short update near the 1.0 release.
|-
|Add your link here
|...
|-
|}

Documentation Team/Notes/1.0

2013-02-03T20:17:24Z

Francis: /* Resources */

Documentation Team/Notes/1.0

2013-02-03T20:16:31Z

Francis: /* Resources */

Documentation Team/Notes/1.0

2013-02-03T20:15:11Z

Francis:

Documentation Team/Notes/1.0

2013-02-03T20:08:25Z

Francis:

Documentation Team/Notes/1.0

2013-02-03T20:07:19Z

Francis: /* Resources */

Documentation Team/Notes/1.0

2013-02-03T19:26:20Z

Francis: /* Schedule */

Documentation Team/Notes/1.0

2013-02-03T19:20:24Z

Francis:

Most part of the Sugar documentation and resources are out-of-date. The idea is to provide Sugar 1.0 with up-to-date documentation.

=Schedule=

Pending to write.

{| cellpadding="10" cellspacing="0" border="1"
!Action
!Status
!Date
|-
|Join all documentation resources
|style="background:#00ff00; color:black" | '''Current'''
| From February 1st 2013
|-
|Add your point here
|To do
| To decide
|-
|Sugar 1.0 Release
|Comming
| Waiting for Sugar 1.0 Release Schedule
|}

=Resources=

There is many documentation, out-of-date and being updated. These are the resources to join and create an only documentaton.

{| cellpadding="10" cellspacing="0" border="1"
!Title
!Status
|-
|[http://en.flossmanuals.net/sugar/ Sugar FLOSS Manual]
|Out of date since 2011
|-
|Add your link here
|...
|-
|}

Documentation Team/Notes/1.0

2013-02-03T18:56:56Z

Francis:

Documentation Team/Notes/1.0

2013-02-03T18:27:56Z

Francis: Created page with "=Sugar 1.0 Documentation Schedule="

=Sugar 1.0 Documentation Schedule=

Translation Team/i18n Best Practices

2013-01-18T16:00:56Z

Francis: Add coding header tip

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }} </noinclude>{{TOCright}}
= General tips =
Here are some general tips which will make your translators happy. For a much more comprehensive list of best practices, please read the [http://live.gnome.org/TranslationProject/DevGuidelines | Gnome i18n Guidelines].
== When in doubt, use translator-comments ==
When you are using a string which may be confusing for the translators (contextual issues, or cultural issues), or if you want the string to be translated according to a particular convention, use translator-comments, which would show up alongside the message in the PO file translator get when they translate you software. Example (from Calculate activity)
<pre>
# TRANS: multiplication symbol (default: '*')
self.mul_sym = _('mul_sym')
</pre>
So as you can see from the above example, translator-comments are normal Python comments with the "TRANS" keyword. This shows up the PO file as
<pre>
#. TRANS: multiplication symbol (default: '*')
#: mathlib.py:74
msgid "mul_sym"
msgstr ""
</pre>

You can also use [http://www.gnu.org/software/gettext/manual/html_node/Contexts.html#Contexts msgctxt], which is better integrated with [http://en.wikipedia.org/wiki/Translation_memory Translation Memory] (T.M.). The output is in this form:
<pre>
#: string ID
msgctxt "button label"
msgid "Edit"
msgstr ""
</pre>

== Use plural forms ==
Do not assume that all languages have a concept of singular and plural like English. Some languages might have a single form, and some have more than two form. Use [http://www.gnu.org/software/gettext/manual/gettext.html#Plural-forms plural forms] via ''ngettext()'' in these cases. Example (from sugar-update-control):
<pre>
header = gettext.ngettext("You can install %s update",
"You can install %s updates", avail) \
% avail
</pre>

== Show changes in strings ==
Use the "--previous" option with msgmerge when updating PO files. This option will output strings like this:
<pre>
#, string header
#|msgid "This is the old string"
msgid "This is the new string"
msgstr "This is the old string translated"
</pre>
so translators can see what has changed. Some translation editors will highlight the changes, which is particularly helpful with complex strings, very long strings or strings with code/formatting. This option definitely improves the accuracy of translation updates.

== Use white-spaces and newlines only when you need to ==

The tool which converts the translated PO files into binary MO files, ''msgfmt'', can be quite picky about newlines and lines with only whitespaces. For example, the following string in sugar has a blank line at the end which is often overlooked by translators, causing msgfmt to choke.
<pre>
print _('Usage: sugar-control-panel [ option ] key [ args ... ] \n\
Control for the sugar environment. \n\
Options: \n\
-h show this help message and exit \n\
-l list all the available options \n\
-h key show information about this key \n\
-g key get the current value of the key \n\
-s key set the current value for the key \n\
-c key clear the current value for the key \n\
')
</pre>

== Keep string formatting as simple as possible ==

In case of code like the following example, translators tend to translate the strings "error" and "file" into their own languages, causing msgfmt to choke.

<pre>
notify.props.msg = _('%(error)s when deleting %(file)s') % \
{ 'error': err.strerror, 'file': logfile }
</pre>

Avoid such strings if possible; use numbers or untranslatable strings (that are not English words) instead, e.g.
<pre>
notify.props.msg = _('%(ERR)s when deleting %(2)s') % \
{ 'ERR': err.strerror, '2': logfile }
</pre>

= Pootle specific tips =
These are some tips/guidelines which would keep [[User:Sayamindu|Sayamindu]] (who currently maintains the Pootle installation) happy ;-).

== Do not touch anything inside your po directory ==

If you change anything inside the po directory (including the POT file), and push it to Git, it will create a conflict which has to be updated in the Pootle side manually. Try avoid doing this, If you see any issues, please ping Sayamindu (sayamindu at sugarlabs dot org) (you can also catch him on IRC, in channels like #sugar on Freenode with the nick unmadindu). If the changeset that you have is large, send him a patch, and he will apply that from the Pootle side manually and commit.

== Try to keep the po directory in the top level directory of your repository ==

The various homebrew helper scripts which keep Pootle running properly make the assume that the po directory will be in the toplevel of the source repository. Try to avoid putting the po directory under a directory like i18n or such, as this will need yet another special casing in the helper scripts, making stuff more difficult to maintain.

== Add user pootle to the committer list for your activity ==

If you have set up your activity on git.suagrlabs.org, please add the user pootle to the committer list so that po files can be updated for your project. (You add new committers from the button "Manage colaborators" in the right-hand menu on the repository mainline page (where you will find a link to http://git.sugarlabs.org/[your activity]/mainline).

== Request to have your project included in pootle ==

Make a request by filing a ticket on bugs.sugarlabs.org. You should set Type to 'task' and Component to 'localization'. Please include a link to the project page on git.sugarlabs.org (or whatever other repository you use).

== Specify the character encoding if necessary ==

Python files with non-ascii characters or declaring strings representing them, need to add the following line to the header.

# -*- coding: utf-8 -*-

If not, the pootle helper won't generate the pot/po files.

Features/GTK3/Porting/Record

2012-12-19T01:22:21Z

Francis:

= Some changes =

'''Replace:'''

def getStringFromPixbuf(pixbuf):
data = [""]
pixbuf.save_to_callback(_saveDataToBufferCb, "png", {}, data)
return base64.b64encode(str(data[0]))

def _saveDataToBufferCb(buf, data):
data[0] += buf
return True

'''With:'''

def getStringFromPixbuf(pixbuf):
"""Converts a pixbuf in a string."""

# Save_to_bufferv return: (bool, string)
data = pixbuf.save_to_bufferv('png', [], [])

return base64.b64encode(data[1])

'''Replace:'''

thumbImg.save(thumbPath, "jpeg", {"quality":"85"} )

'''With:'''

thumbImg.savev(thumbPath, "jpeg", {"quality":"85"} )

'''Replace:'''

def load_colored_svg(filename, stroke, fill):
path = os.path.join(constants.GFX_PATH, filename)
data = open(path, 'r').read()

entity = '<!ENTITY fill_color "%s">' % fill
data = re.sub('<!ENTITY fill_color .*>', entity, data)

entity = '<!ENTITY stroke_color "%s">' % stroke
data = re.sub('<!ENTITY stroke_color .*>', entity, data)

"""return rsvg.Handle(data=data).get_pixbuf()"""

'''With:'''

def load_colored_svg(filename, stroke, fill):
"""Loads an svg, will change the fill and
stroke colors and returns the pixbuf."""

path = os.path.join(constants.GFX_PATH, filename)
data = open(path, 'r').read()

entity = '<!ENTITY fill_color "%s">' % fill
data = re.sub('<!ENTITY fill_color .*>', entity, data)

entity = '<!ENTITY stroke_color "%s">' % stroke
data = re.sub('<!ENTITY stroke_color .*>', entity, data)

"""return Rsvg.Handle.new_from_data(data.encode('utf-8')).get_pixbuf()"""

'''Not implement:'''

super(Record, self).close()

Due to: [http://bugs.sugarlabs.org/ticket/4345 SL#4345]

=From Pixmap to Pixbuf=
When an application fails and you want to close from the corresponding button occurs:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/sugar3/activity/activity.py", line 890, in _keep_failed_dialog_response_cb
self.close(skip_save=True)
TypeError: close() got an unexpected keyword argument 'skip_save'
And the activity is not closed, nor can restart sugar as alert reappears again and again, you need to stop.

==This error is caused because:==
When a class B inherits from class A, and
in B is overwritten a function of A,
A function is no longer running,
but instead runs the function of the class B,
even when explicitly call function A from B.

The solution is in using Pixbuf instead of Pixmap:

'''Replace:'''

def _generate_image(self, num):
w = 55
h = w
pixmap = gdk.Pixmap(self.get_window(), w, h, -1)
ctx = pixmap.cairo_create()
ctx.rectangle(0, 0, w, h)
ctx.set_source_rgb(0, 0, 0)
ctx.fill()

'''By:'''
def _generate_image(self, num):

w = 55
h = w

x, y = self.get_property('window').get_position()
rect = self.get_allocation()
width, height = rect.width, rect.height

thumb_surface = Gdk.Window.create_similar_surface(
self.get_property('window'),
cairo.CONTENT_COLOR,
width, height)

ctx = cairo.Context(thumb_surface)

Gdk.cairo_set_source_window(
cairo_context,
self.get_property('window'),
x, y)

ctx.paint()

ctx.rectangle(x, y, w, h)
ctx.set_source_rgb(0, 0, 0)
ctx.fill()

User:Francis/2013 SLOBS Platform

2012-12-11T00:38:34Z

Francis: /* 2 Deployment frustrations */

See a Spanish version at the end.

= Sugar Labs Oversight Board candidacy platform 2012-2013 =

Some people requested me to stand as candidate for election to the Sugar Labs Oversight Board. Their reasons were that Sugar needs the viewpoint of somebody who is/was part of a classroom with OLPC-XO/Sugar.

== Some information about myself ==

I'm a student in Uruguay. I received an XO-1 when I was in form 5 of school, at about ten-years-old.

Two years ago, I joined the Uruguayan OLPC community (CeibalJAM) which has a great mailing list where users and developers collaborate. That's a good place to get really involved into a development process, and do a transition between Sugar user and an activity developer. Some months ago I met some of the current Sugar maintainers and code contributors. Having the possibility to solve the problems that I noticed when developing activities, I started to contribute to Sugar itself. I'm also administrator of the OLPC-Sur mailing list, which in some ways is a Spanish version of IAEP.

== Daniel Francis viewpoint about Sugar ==

=== 1 The success and reason of Sugar ===

We all know Sugar can be an excellent learning platform that can be discovered by children, providing an excellent experience and getting great results (when the laptops are used successfully). I consider the work on Sugar itself is already done, but when new features are coming to Sugar thanks to Activity Central, OLPC and our volunteer contributors, Sugar needs the design team to look again at the current Sugar interface and do maintenence on the big work done on the interface.

=== 2 Deployment frustrations ===

The biggest frustration of OLPC in schools is the low use. A big percent of the laptops with Sugar aren't used in schools toward educational objectives, due to some reasons that Sugar must face.

==== 2.1 Identify the reasons ====

This is part of the learning team. Sugar Labs needs to know why some teachers don't like to teach with XOs. The biggest issues are related to the software and content. Taking this into account, Sugar Labs would be able to make action items and improve the software.

==== 2.2 Time ====

Sugar is not intended to be a productivity environment, but the spent time is the reason of why only a very small percentage of highschool teachers in Uruguay are implementing technology in their classroom. They have 45 minutes per class, and a long list of content to have taught by the end of the year, so the most comfortable and fast model results to be the traditional class, and have no opportunities or time to try and discover the environment like the children could.

Here Sugar needs work in usability and accessibility, not only simplicity, because it is not about limitations in understanding.

The work in classroom needs to be fast and easy trough improving the usability in activities like Browse, Write, Paint, Labyrinth, et al. but there are other activities such as TurtleBlocks or Scratch that are valid for spending extra time in longer classes or homework.

==== 2.3 Training of teachers ====

The main problem of an interface made to be discovered is that it can't be used by people who don't want to discover it.

This is the case of a big part of the teachers. Their only tool to learn how to use Sugar and the only way to interest them in using Sugar in their classroom is through teaching training. This is something which doesn't depend of Sugar Labs, but the current Sugar documentation is not maintained, and could be converted in the best place for the teachers to spend time learning.

=== 3 School content adaptation ===

The current tools can be adapted by each teacher to their educational requirements. As an example, children can write better and learn to write by using the Write activity better than writting in a piece of paper, because with the Write activity they can organise their ideas and move the paragraphs to make a well written text. Sugar needs a way to show the teachers these advantages and perhaps it's through improving the documentation that this can be achieved.

Some new activities need to be created keeping in mind the school program items, good examples are the "I know ..." activities, related to geography.

= Plataforma de candidatura para el Sugar Labs Oversight Board 2012-2013 =

Algunas personas me pidieron que me presentara como candidato para las elecciones del Sugar Labs Oversight Board. Sus motivos fueron que Sugar necesita el punto de vista de alguien que es/fue parte de una clase con OLPC-XO/Sugar.

== Algo de información sobre mí ==

Soy un estudiante de Uruguay. Recibí una XO-1 cuando estaba en quinto año de escuela, con 10 años.

Hace dos años, me uní a la comunidad uruguaya de OLPC (CeibalJAM) la cual posee una lista de correo donde los usuarios y desarrolladores trabajan en conjunto. Es un buen lugar para involucrarse realmente en un proceso de desarrollo y hacer una transición de usuario de Sugar a desarrollador de actividades para Sugar. Hace algunos meses conocí algunos de los desarrolladores mantienen el entorno Sugar. Teniendo la posibilidad de resolver problemas que encontré al desarrollar actividades, comencé a contribuir al entorno Sugar mismo. Además soy administrador de la lista de correo OLPC-Sur, que en pocas palabras es una versión en español de IAEP.

== El punto de vista de Daniel Francis sobre Sugar ==

=== 1 El éxito y motivo de Sugar ===

Todos sabemos que Sugar puede ser una plataforma de aprendizaje excelente para que los niños la descubran, proporcionando una experiencia muy buena y dando muy buenos resultados (cuando las laptops se usan exitosamente). Considero que ese trabajo en Sugar ya está hecho; pero cuando nuevas características llegan a Sugar gracias a Activity Central, OLPC y los colaboradores voluntarios, Sugar necesita al equipo de diseño para mirar nuevamente la interfaz actual y conservar el enorme trabajo hecho en ella.

=== 2 Frustraciones del despliegue ===

La frustración más grande de OLPC en las escuelas es el escaso uso de las máquinas. Un gran porcentaje de las laptops con Sugar no se usa en las escuelas con objetivos educativos, por algunas razones que Sugar debe encarar.

==== 2.1 Identificar las razones ====

Esto es parte del equipo de aprendizaje. Sugar Labs necesita conocer por qué a los docentes no les gusta enseñar con las XO. Los problemas más grandes están relacionados con el software y contenido. Teniendo esto en cuenta, Sugar Labs puede actuar para mejorar el software.

==== 2.2 Tiempo ====

Sugar no pretende ser un entorno de productividad, pero el tiempo gastado es el motivo de por qué solo una muy pequeña parte de los docentes en Uruguay usan Sugar en sus aulas. Tienen clases de 45 minutos y una lista larga de contenidos para haber sido enseñados a fin de año, por lo tanto el modelo más cómodo y rápido resulta ser la clase tradicional. No tienen oportunidades o tiempo de probar y descubrir un entorno como los niños pueden.

Aquí Sugar necesita trabajo en usabilidad y accesibilidad, no solo simplicidad porque eso no significa limitar las posibilidades de los usuarios.

El trabajo en clase necesita ser ágil y facil a través de mejorar la usabilidad en actividades como Navegar, Escribir, Pintar, Laberinto, etc. pero hay otras actividades como TortugArte y Scratch que son válidas para gastar tiempo extra en clases más largas y tarea domiciliaria.

==== 2.3 Formación docente ====

El problema principal de una interfaz hecha para ser descubierta es que no pueden usarla las personas que no quieran descubrirla.

Ese es el caso de una gran parte de los docentes. Su única herramienta para aprender cómo usar Sugar y la única forma de interesarlos en usar Sugar en sus aulas de clase es a través de los cursos de capacitación. Esto es algo que no depende de Sugar Labs; pero nadie mantiene la documentación de Sugar actual y podría convertirse en el mejor lugar para que los docentes gasten tiempo aprendiendo.

=== 3 Adaptación al contenido escolar ===

Las herramientas actuales pueden adaptarse por cada docente a sus requerimientos y necesidades educativas. Por ejemplo, los niños pueden redactar mejor y aprender a redactar textos con la actividad Escribir mejor que con una hoja de papel, porque con la actividad Escribir ellos tienen la posibilidad de organizar sus ideas y mover los párrafos para crear un texto bien redactado. Sugar necesita una forma de mostrarle a los docentes estas ventajas y esto podría lograrse quizas mejorando la documentación.

Necesitan crearse algunas actividades nuevas teniendo en cuenta los temas de los programas escolares, buenos ejemplos son las actividades "Conozco ...", relacionadas con geografía.

Oversight Board/2012-2013-candidates

2012-12-11T00:18:51Z

Francis: /* Candidates */

<noinclude>[[Category:Oversight board]]
[[Category:Governance]]
[[Category:Team]]
</noinclude>

==Election==
Four (4) seats are open ([[Sugar Labs/Governance#Oversight_Board|due to staggered seat terms]]) for election / re-election to the [[Oversight Board|Sugar Labs Oversight Board]] for 2012-2013, those of Chris Ball, Aleksey Lim, Adam Holt, and Sebastian Silva.

==Candidates==
Here are the candidates:

* [http://google.com/search?q=adam+holt+mit Adam Holt] ([[User:Holt|7-point platform]])
* [[User:Godiard|Gonzalo Odiard]] ([[User:Godiard/SugarOversightCandidacy2012|platform]])
* [http://wiki.laptop.org/go/User:Claudia_Urrea Claudia Urrea]
* Sebastian Silva
* [[User:Yamaplos|Yama Ploskonka]] ([[User:Yamaplos/Make-The-Teacher-Job-Easier | Make The Teacher's Job Easier platform]])
* [[User:Francis|S. Daniel Francis]] ([[User:Francis/2013_SLOBS_Platform|platform]])
* '''Your name''' (''link to your platform'')

==References==
* [[Oversight_Board/2011-2012-candidates]]
* [[Oversight_Board/2010-2011-candidates]]
* [[Oversight_Board/2009-2010-candidates]]
* [[Sugar Labs/Members]]

User:Francis/2013 SLOBS Platform

2012-12-11T00:15:11Z

Francis: Created page with "See a Spanish version at the end. = Sugar Labs Oversight Board candidacy platform 2012-2013 = Some people requested me to stand as candidate for election to the Sugar Labs O..."

See a Spanish version at the end.

= Sugar Labs Oversight Board candidacy platform 2012-2013 =

Some people requested me to stand as candidate for election to the Sugar Labs Oversight Board. Their reasons were that Sugar needs the viewpoint of somebody who is/was part of a classroom with OLPC-XO/Sugar.

== Some information about myself ==

I'm a student in Uruguay. I received an XO-1 when I was in form 5 of school, at about ten-years-old.

Two years ago, I joined the Uruguayan OLPC community (CeibalJAM) which has a great mailing list where users and developers collaborate. That's a good place to get really involved into a development process, and do a transition between Sugar user and an activity developer. Some months ago I met some of the current Sugar maintainers and code contributors. Having the possibility to solve the problems that I noticed when developing activities, I started to contribute to Sugar itself. I'm also administrator of the OLPC-Sur mailing list, which in some ways is a Spanish version of IAEP.

== Daniel Francis viewpoint about Sugar ==

=== 1 The success and reason of Sugar ===

We all know Sugar can be an excellent learning platform that can be discovered by children, providing an excellent experience and getting great results (when the laptops are used successfully). I consider the work on Sugar itself is already done, but when new features are coming to Sugar thanks to Activity Central, OLPC and our volunteer contributors, Sugar needs the design team to look again at the current Sugar interface and do maintenence on the big work done on the interface.

=== 2 Deployment frustrations ===

The biggest frustration regarding OLPC in schools is the low use. A big percent of the laptops with Sugar aren't used in schools toward educational objectives, due to some reasons that Sugar must face.

==== 2.1 Identify the reasons ====

This is part of the learning team. Sugar Labs needs to know why some teachers don't like to teach with XOs. The biggest issues are related to the software and content. Taking this into account, Sugar Labs would be able to make action items and improve the software.

==== 2.2 Time ====

Sugar is not intended to be a productivity environment, but the spent time is the reason of why only a very small percentage of highschool teachers in Uruguay are implementing technology in their classroom. They have 45 minutes per class, and a long list of content to have taught by the end of the year, so the most comfortable and fast model results to be the traditional class, and have no opportunities or time to try and discover the environment like the children could.

Here Sugar needs work in usability and accessibility, not only simplicity, because it is not about limitations in understanding.

The work in classroom needs to be fast and easy trough improving the usability in activities like Browse, Write, Paint, Labyrinth, et al. but there are other activities such as TurtleBlocks or Scratch that are valid for spending extra time in longer classes or homework.

==== 2.3 Training of teachers ====

The main problem of an interface made to be discovered is that it can't be used by people who don't want to discover it.

This is the case of a big part of the teachers. Their only tool to learn how to use Sugar and the only way to interest them in using Sugar in their classroom is through teaching training. This is something which doesn't depend of Sugar Labs, but the current Sugar documentation is not maintained, and could be converted in the best place for the teachers to spend time learning.

=== 3 School content adaptation ===

The current tools can be adapted by each teacher to their educational requirements. As an example, children can write better and learn to write by using the Write activity better than writting in a piece of paper, because with the Write activity they can organise their ideas and move the paragraphs to make a well written text. Sugar needs a way to show the teachers these advantages and perhaps it's through improving the documentation that this can be achieved.

Some new activities need to be created keeping in mind the school program items, good examples are the "I know ..." activities, related to geography.

= Plataforma de candidatura para el Sugar Labs Oversight Board 2012-2013 =

Algunas personas me pidieron que me presentara como candidato para las elecciones del Sugar Labs Oversight Board. Sus motivos fueron que Sugar necesita el punto de vista de alguien que es/fue parte de una clase con OLPC-XO/Sugar.

== Algo de información sobre mí ==

Soy un estudiante de Uruguay. Recibí una XO-1 cuando estaba en quinto año de escuela, con 10 años.

Hace dos años, me uní a la comunidad uruguaya de OLPC (CeibalJAM) la cual posee una lista de correo donde los usuarios y desarrolladores trabajan en conjunto. Es un buen lugar para involucrarse realmente en un proceso de desarrollo y hacer una transición de usuario de Sugar a desarrollador de actividades para Sugar. Hace algunos meses conocí algunos de los desarrolladores mantienen el entorno Sugar. Teniendo la posibilidad de resolver problemas que encontré al desarrollar actividades, comencé a contribuir al entorno Sugar mismo. Además soy administrador de la lista de correo OLPC-Sur, que en pocas palabras es una versión en español de IAEP.

== El punto de vista de Daniel Francis sobre Sugar ==

=== 1 El éxito y motivo de Sugar ===

Todos sabemos que Sugar puede ser una plataforma de aprendizaje excelente para que los niños la descubran, proporcionando una experiencia muy buena y dando muy buenos resultados (cuando las laptops se usan exitosamente). Considero que ese trabajo en Sugar ya está hecho; pero cuando nuevas características llegan a Sugar gracias a Activity Central, OLPC y los colaboradores voluntarios, Sugar necesita al equipo de diseño para mirar nuevamente la interfaz actual y conservar el enorme trabajo hecho en ella.

=== 2 Frustraciones del despliegue ===

La frustración más grande de OLPC en las escuelas es el escaso uso de las máquinas. Un gran porcentaje de las laptops con Sugar no se usa en las escuelas con objetivos educativos, por algunas razones que Sugar debe encarar.

==== 2.1 Identificar las razones ====

Esto es parte del equipo de aprendizaje. Sugar Labs necesita conocer por qué a los docentes no les gusta enseñar con las XO. Los problemas más grandes están relacionados con el software y contenido. Teniendo esto en cuenta, Sugar Labs puede actuar para mejorar el software.

==== 2.2 Tiempo ====

Sugar no pretende ser un entorno de productividad, pero el tiempo gastado es el motivo de por qué solo una muy pequeña parte de los docentes en Uruguay usan Sugar en sus aulas. Tienen clases de 45 minutos y una lista larga de contenidos para haber sido enseñados a fin de año, por lo tanto el modelo más cómodo y rápido resulta ser la clase tradicional. No tienen oportunidades o tiempo de probar y descubrir un entorno como los niños pueden.

Aquí Sugar necesita trabajo en usabilidad y accesibilidad, no solo simplicidad porque eso no significa limitar las posibilidades de los usuarios.

El trabajo en clase necesita ser ágil y facil a través de mejorar la usabilidad en actividades como Navegar, Escribir, Pintar, Laberinto, etc. pero hay otras actividades como TortugArte y Scratch que son válidas para gastar tiempo extra en clases más largas y tarea domiciliaria.

==== 2.3 Formación docente ====

El problema principal de una interfaz hecha para ser descubierta es que no pueden usarla las personas que no quieran descubrirla.

Ese es el caso de una gran parte de los docentes. Su única herramienta para aprender cómo usar Sugar y la única forma de interesarlos en usar Sugar en sus aulas de clase es a través de los cursos de capacitación. Esto es algo que no depende de Sugar Labs; pero nadie mantiene la documentación de Sugar actual y podría convertirse en el mejor lugar para que los docentes gasten tiempo aprendiendo.

=== 3 Adaptación al contenido escolar ===

Las herramientas actuales pueden adaptarse por cada docente a sus requerimientos y necesidades educativas. Por ejemplo, los niños pueden redactar mejor y aprender a redactar textos con la actividad Escribir mejor que con una hoja de papel, porque con la actividad Escribir ellos tienen la posibilidad de organizar sus ideas y mover los párrafos para crear un texto bien redactado. Sugar necesita una forma de mostrarle a los docentes estas ventajas y esto podría lograrse quizas mejorando la documentación.

Necesitan crearse algunas actividades nuevas teniendo en cuenta los temas de los programas escolares, buenos ejemplos son las actividades "Conozco ...", relacionadas con geografía.

User:Francis

2012-12-09T19:06:04Z

Francis:

Location: Montevideo, Uruguay.

Ocupation: Student.

Email: Daniel Francis <francis at sugarlabs dot org>

ASLO User: http://activities.sugarlabs.org/es-ES/sugar/user/5067

My files: http://people.sugarlabs.org/francis/

== I Maintain ==
* [[Activities/Graph_Plotter|Graph Plotter]] - Mathematical function plotter.
* [[Activities/Terminal|Terminal]] - Command line (Only commiter)
* [[Activity_Team/Sweetener| Sweetener]] - Desktop framework. (In progress)

== Contributions ==
==== Sugar Artwork ====
* 'Modern' tabs ([http://bugs.sugarlabs.org/ticket/3923 SL#3923])
==== Sugar Toolkit ====
* Enable to use the property "accelerator" in ToggleToolButton
==== Turtle Art ====
* Port to Gtk3
==== Speak ====
* Lots of Pep8 corrections
* Remove old toolkit modules
* Remove HippoCanvas
==== Terminal ====
* Port to Gtk3
* Same tabs as Browse
* Maintain the unstable gtk3 branch

User:Francis

2012-12-09T19:03:21Z

Francis: /* I Maintain */

Email: Daniel Francis <francis at sugarlabs dot org>

ASLO User: http://activities.sugarlabs.org/es-ES/sugar/user/5067

My files: http://people.sugarlabs.org/francis/

== I Maintain ==
* [[Activities/Graph_Plotter|Graph Plotter]] - Mathematical function plotter.
* [[Activities/Terminal|Terminal]] - Command line (Only commiter)
* [[Activity_Team/Sweetener| Sweetener]] - Desktop framework. (In progress)

== Contributions ==
==== Sugar Artwork ====
* 'Modern' tabs ([http://bugs.sugarlabs.org/ticket/3923 SL#3923])
==== Sugar Toolkit ====
* Enable to use the property "accelerator" in ToggleToolButton
==== Turtle Art ====
* Port to Gtk3
==== Speak ====
* Lots of Pep8 corrections
* Remove old toolkit modules
* Remove HippoCanvas
==== Terminal ====
* Port to Gtk3
* Same tabs as Browse
* Maintain the unstable gtk3 branch

Activity Team/Sweetener

2012-11-04T22:12:23Z

Francis: /* Documentation */

Sweetener is a desktop framework which provides compatibility between Sugar and other Desktops. Does all the repetitive parts, for be more friendly with developers. It's divided in modules, they can be included in an activity for do a specific task.

== Maintainers ==
*[[User:Francis|Daniel Francis]]

== Current Release ==
At the moment it hasn't got a stable release. Clone the [http://git.sugarlabs.org/sweetener GIT Repository] and feel free to send patches, request merges or contact the maintainers.

== Documentation ==

The Sweetener documentation is available in [http://people.sugarlabs.org/francis/sweetenerdoc].

Its source code is in Git:
http://git.sugarlabs.org/sweetener/doc

== Get started creating an activity==
* Start a repository on [http://git.sugarlabs.org/ Git]
* Clone Sweetener
$ git clone git://git.sugarlabs.org/sweetener/sweetener.git
* Copy to your new activity directory the following files:
Makefile
activity.py
canvas.py
info.py
options.py
setup.py
Optional, only if you want to get your activity working on other Linux desktops:
application.py
hello-integration # (rename it to your activity name)
* Make the following directories inside your activity:
activity/
sugar/
desktop/ # (Only if you want to run your activity on Linux desktops)
* Clone sweetener submodules
$ git submodule add git://git.sugarlabs.org/sweetener/makescripts
$ git submodule add git://git.sugarlabs.org/sweetener/sugar sugar/sweetener

# This is only for other Linux desktops.
$ git submodule add git://git.sugarlabs.org/sweetener/desktop desktop/sweetener

* Fill info.py with information about your activity. See [[Activity_Team/Sweetener#Activity_information|info.py fields]].
* Create a sugarized icon on activity/activity-(lower-name).svg where lower-name must be the same as the variable on info.py
* Generate the activity.info file trough the command make.
$ make activity
* Install it
$ python setup.py dev
* Make a .xo bundle
$ make xo_bundle
* Make a desktop tarball
$ make dist_tarball

== Activity information ==
The way to tell the framework scripts and all your program some data is through the file info.py

We recommend a text search for fill the following fields:

* Activity Service Name
* IO Mode Document or Config. Important at desktops.
* Generic Name Only for desktops. See examples at the file comments.
* Activity Name
* lower-name
* copyright note (Obligatory for desktops, recommended)
* Version
* Summary
* Authors
* If any, Web site and documentation URL (Only for desktops)
* Categories (Only for desktops)
* Filter Important on desktops with IO mode Document, also needed to create your own mimetype.
* license name

== Key accelerators ==
Gtk Stock sets by default some accelerators for convention, like Ctrl+Q for Quit.
Sweetener sets and overwrites some key accelerators for integrate them with Sugar. 
Keep this in mind when setting up key accelerators in your activity.
At your convenience, edit files sugar/sweetener/stock.py and desktop/sweetener/stock.py.

{| class="wikitable"
|-
! '''Stock label''' !! '''Key accelerator on Sugar''' !! '''Key accelerator on Linux desktops'''
|-
| Add || Ctrl + A || Ctrl + A
|-
| Fullscreen || Alt + Return || F11
|-
| Normal Size || Ctrl + 0 || Ctrl + 0
|-
| Remove || Shift + Del || Ctrl + R
|-
| Save as || Unused :) || Ctrl + Shift + S
|-
| Select Color || Ctrl + L || Ctrl + L
|-
| Zoom In || Ctrl + + || Ctrl + +
|-
| Zoom Out || Ctrl + - || Ctrl + -
|}

== Activities using Sweetener==
* [[Activities/Graph_Plotter|Graph Plotter]]
* [http://git.sugarlabs.org/illustrate-sugar-integration/illustrate-sweetener Illustrate Sweetener] (Development)

== Gtk2 and Gtk3 Support ==
There are efforts to port Sweetener to Gtk3[http://git.sugarlabs.org/sudoku/mainline], but at the moment it isn't possible thanks to the upstream bug [https://bugzilla.gnome.org/show_bug.cgi?id=652697 GNOME#652697].

Activity Team/Sweetener

2012-11-04T22:11:50Z

Francis: /* Documentation */

Sweetener is a desktop framework which provides compatibility between Sugar and other Desktops. Does all the repetitive parts, for be more friendly with developers. It's divided in modules, they can be included in an activity for do a specific task.

== Maintainers ==
*[[User:Francis|Daniel Francis]]

== Current Release ==
At the moment it hasn't got a stable release. Clone the [http://git.sugarlabs.org/sweetener GIT Repository] and feel free to send patches, request merges or contact the maintainers.

== Documentation ==

The Sweetener documentation is available in [http://people.sugarlabs.org/francis/sweetenerdoc].
Its source code is in Git:
http://git.sugarlabs.org/sweetener/doc

== Get started creating an activity==
* Start a repository on [http://git.sugarlabs.org/ Git]
* Clone Sweetener
$ git clone git://git.sugarlabs.org/sweetener/sweetener.git
* Copy to your new activity directory the following files:
Makefile
activity.py
canvas.py
info.py
options.py
setup.py
Optional, only if you want to get your activity working on other Linux desktops:
application.py
hello-integration # (rename it to your activity name)
* Make the following directories inside your activity:
activity/
sugar/
desktop/ # (Only if you want to run your activity on Linux desktops)
* Clone sweetener submodules
$ git submodule add git://git.sugarlabs.org/sweetener/makescripts
$ git submodule add git://git.sugarlabs.org/sweetener/sugar sugar/sweetener

# This is only for other Linux desktops.
$ git submodule add git://git.sugarlabs.org/sweetener/desktop desktop/sweetener

* Fill info.py with information about your activity. See [[Activity_Team/Sweetener#Activity_information|info.py fields]].
* Create a sugarized icon on activity/activity-(lower-name).svg where lower-name must be the same as the variable on info.py
* Generate the activity.info file trough the command make.
$ make activity
* Install it
$ python setup.py dev
* Make a .xo bundle
$ make xo_bundle
* Make a desktop tarball
$ make dist_tarball

== Activity information ==
The way to tell the framework scripts and all your program some data is through the file info.py

We recommend a text search for fill the following fields:

* Activity Service Name
* IO Mode Document or Config. Important at desktops.
* Generic Name Only for desktops. See examples at the file comments.
* Activity Name
* lower-name
* copyright note (Obligatory for desktops, recommended)
* Version
* Summary
* Authors
* If any, Web site and documentation URL (Only for desktops)
* Categories (Only for desktops)
* Filter Important on desktops with IO mode Document, also needed to create your own mimetype.
* license name

== Key accelerators ==
Gtk Stock sets by default some accelerators for convention, like Ctrl+Q for Quit.
Sweetener sets and overwrites some key accelerators for integrate them with Sugar. 
Keep this in mind when setting up key accelerators in your activity.
At your convenience, edit files sugar/sweetener/stock.py and desktop/sweetener/stock.py.

{| class="wikitable"
|-
! '''Stock label''' !! '''Key accelerator on Sugar''' !! '''Key accelerator on Linux desktops'''
|-
| Add || Ctrl + A || Ctrl + A
|-
| Fullscreen || Alt + Return || F11
|-
| Normal Size || Ctrl + 0 || Ctrl + 0
|-
| Remove || Shift + Del || Ctrl + R
|-
| Save as || Unused :) || Ctrl + Shift + S
|-
| Select Color || Ctrl + L || Ctrl + L
|-
| Zoom In || Ctrl + + || Ctrl + +
|-
| Zoom Out || Ctrl + - || Ctrl + -
|}

== Activities using Sweetener==
* [[Activities/Graph_Plotter|Graph Plotter]]
* [http://git.sugarlabs.org/illustrate-sugar-integration/illustrate-sweetener Illustrate Sweetener] (Development)

== Gtk2 and Gtk3 Support ==
There are efforts to port Sweetener to Gtk3[http://git.sugarlabs.org/sudoku/mainline], but at the moment it isn't possible thanks to the upstream bug [https://bugzilla.gnome.org/show_bug.cgi?id=652697 GNOME#652697].

File:GraphPlotterDesktop.tar.gz

2012-11-04T13:05:36Z

Francis: Blanked the page

File:GraphPlotterDesktop.tar.gz

2012-11-04T13:04:32Z

Francis: uploaded a new version of "File:GraphPlotterDesktop.tar.gz": Reverted to version as of 19:33, 7 September 2012

This is the current release of Graph Plotter for Linux Desktops.

Activities/Graph Plotter

2012-11-04T12:54:07Z

Francis: /* Desktop Version */

<noinclude>
{{Translations
| [[Activities/Graph_Plotter/lang-es|español]] }}{{TOCright}}</noinclude>

Graph Plotter is an activity for plot mathematical functions easily.

[[Image:GraphPlotterIcon.svg]]

== Download ==

[http://git.sugarlabs.org/graph-plotter/mainline.git GIT repository]
[http://activities.sugarlabs.org//en-US/sugar/addon/4591 ASLO]

==== Desktop Version ====

http://people.sugarlabs.org/francis/graph-plotter/graph-plotter-8.tar.gz

See [[Activities/Graph_Plotter#Running_Graph_Plotter_on_other_Linux_environments|Running Graph Plotter on other Linux environments]] for more information.

== Maintainers ==
*[[User:Francis|Daniel Francis]]

== Story ==

The starter idea was from Ana Cichero, a maths teacher from Uruguay. Here students can't pay an expensive calculator, but their little siblings have XO computers and she needed an activity easy to use where her students can do their homework or revise previous than their tests. Now there are advanced students with XO computers and this activity is very useful for them.

== Running Graph Plotter on other Linux environments ==
Dependencies:
python-rsvg
python-numpy

Steps:
<ul>
<li>Downolad and extract the file [[File:GraphPlotterDesktop.tar.gz]].</li>
<li>Open the extracted dir and run the install script.</li>
</ul>
Instead the last step, by the console you can type:

make install

== Screenshots ==
==== On Sugar ====
[[Image:GraphPlotterScreenshot.png|700px]]
==== On other Linux desktops ====
[[Image: GraphPlotterDesktop.png|700px]]

Activities/Graph Plotter

2012-11-04T12:48:58Z

Francis: /* Maintainers */

<noinclude>
{{Translations
| [[Activities/Graph_Plotter/lang-es|español]] }}{{TOCright}}</noinclude>

Graph Plotter is an activity for plot mathematical functions easily.

[[Image:GraphPlotterIcon.svg]]

== Download ==

[http://git.sugarlabs.org/graph-plotter/mainline.git GIT repository]
[http://activities.sugarlabs.org//en-US/sugar/addon/4591 ASLO]

==== Desktop Version ====
(Current version available: 8)
[[File:GraphPlotterDesktop.tar.gz]]
See [[Activities/Graph_Plotter#Running_Graph_Plotter_on_other_Linux_environments|Running Graph Plotter on other Linux environments]] for more information.

== Maintainers ==
*[[User:Francis|Daniel Francis]]

== Story ==

The starter idea was from Ana Cichero, a maths teacher from Uruguay. Here students can't pay an expensive calculator, but their little siblings have XO computers and she needed an activity easy to use where her students can do their homework or revise previous than their tests. Now there are advanced students with XO computers and this activity is very useful for them.

== Running Graph Plotter on other Linux environments ==
Dependencies:
python-rsvg
python-numpy

Steps:
<ul>
<li>Downolad and extract the file [[File:GraphPlotterDesktop.tar.gz]].</li>
<li>Open the extracted dir and run the install script.</li>
</ul>
Instead the last step, by the console you can type:

make install

== Screenshots ==
==== On Sugar ====
[[Image:GraphPlotterScreenshot.png|700px]]
==== On other Linux desktops ====
[[Image: GraphPlotterDesktop.png|700px]]

User:Francis

2012-11-03T00:07:51Z

Francis:

Email: Daniel Francis <francis at sugarlabs dot org>

ASLO User: http://activities.sugarlabs.org/es-ES/sugar/user/5067

My files: http://people.sugarlabs.org/francis/

== I Maintain ==
* [[Activities/Graph_Plotter|Graph Plotter]] - Mathematical function plotter.
* [[Activity_Team/Sweetener| Sweetener]] - Desktop framework. (In progress)

== Contributions ==
==== Sugar Artwork ====
* 'Modern' tabs ([http://bugs.sugarlabs.org/ticket/3923 SL#3923])
==== Sugar Toolkit ====
* Enable to use the property "accelerator" in ToggleToolButton
==== Turtle Art ====
* Port to Gtk3
==== Speak ====
* Lots of Pep8 corrections
* Remove old toolkit modules
* Remove HippoCanvas
==== Terminal ====
* Port to Gtk3
* Same tabs as Browse
* Maintain the unstable gtk3 branch

User:Daniel Francis

2012-11-02T23:31:29Z

Francis: Redirected page to User:Francis

#REDIRECT [[User:Francis]]

User:Daniel Francis

2012-11-02T23:30:47Z

Francis: Redirected page to Francis

#REDIRECT [[Francis]]

User:Francis

2012-11-02T23:29:00Z

Francis: Created page with "Email: Daniel Francis <francis at sugarlabs dot org> ASLO User: http://activities.sugarlabs.org/es-ES/sugar/user/5067 My files: http://people.sugarlabs.org/francis/ == I ..."

Email: Daniel Francis <francis at sugarlabs dot org> 
ASLO User: http://activities.sugarlabs.org/es-ES/sugar/user/5067
My files: http://people.sugarlabs.org/francis/

== I Maintain ==
* [[Activities/Graph_Plotter|Graph Plotter]] - Mathematical function plotter.
* [[Activity_Team/Sweetener| Sweetener]] - Desktop framework. (In progress)

== Contributions ==
==== Sugar Artwork ====
* 'Modern' tabs ([http://bugs.sugarlabs.org/ticket/3923 SL#3923])
==== Sugar Toolkit ====
* Enable to use the property "accelerator" in ToggleToolButton
==== Turtle Art ====
* Port to Gtk3
==== Speak ====
* Lots of Pep8 corrections
* Remove old toolkit modules
* Remove HippoCanvas
==== Terminal ====
* Port to Gtk3
* Same tabs as Browse
* Maintain the unstable gtk3 branch

Activity Team/Sweetener

2012-11-02T23:25:15Z

Francis: /* Maintainers */

Sweetener is a desktop framework which provides compatibility between Sugar and other Desktops. Does all the repetitive parts, for be more friendly with developers. It's divided in modules, they can be included in an activity for do a specific task.

== Maintainers ==
*[[User:Francis|Daniel Francis]]

== Current Release ==
At the moment it hasn't got a stable release. Clone the [http://git.sugarlabs.org/sweetener GIT Repository] and feel free to send patches, request merges or contact the maintainers.

== Documentation ==

It's in the Git repository:
http://git.sugarlabs.org/sweetener/doc
See the README file for generating instructions.

== Get started creating an activity==
* Start a repository on [http://git.sugarlabs.org/ Git]
* Clone Sweetener
$ git clone git://git.sugarlabs.org/sweetener/sweetener.git
* Copy to your new activity directory the following files:
Makefile
activity.py
canvas.py
info.py
options.py
setup.py
Optional, only if you want to get your activity working on other Linux desktops:
application.py
hello-integration # (rename it to your activity name)
* Make the following directories inside your activity:
activity/
sugar/
desktop/ # (Only if you want to run your activity on Linux desktops)
* Clone sweetener submodules
$ git submodule add git://git.sugarlabs.org/sweetener/makescripts
$ git submodule add git://git.sugarlabs.org/sweetener/sugar sugar/sweetener

# This is only for other Linux desktops.
$ git submodule add git://git.sugarlabs.org/sweetener/desktop desktop/sweetener

* Fill info.py with information about your activity. See [[Activity_Team/Sweetener#Activity_information|info.py fields]].
* Create a sugarized icon on activity/activity-(lower-name).svg where lower-name must be the same as the variable on info.py
* Generate the activity.info file trough the command make.
$ make activity
* Install it
$ python setup.py dev
* Make a .xo bundle
$ make xo_bundle
* Make a desktop tarball
$ make dist_tarball

== Activity information ==
The way to tell the framework scripts and all your program some data is through the file info.py

We recommend a text search for fill the following fields:

* Activity Service Name
* IO Mode Document or Config. Important at desktops.
* Generic Name Only for desktops. See examples at the file comments.
* Activity Name
* lower-name
* copyright note (Obligatory for desktops, recommended)
* Version
* Summary
* Authors
* If any, Web site and documentation URL (Only for desktops)
* Categories (Only for desktops)
* Filter Important on desktops with IO mode Document, also needed to create your own mimetype.
* license name

== Key accelerators ==
Gtk Stock sets by default some accelerators for convention, like Ctrl+Q for Quit.
Sweetener sets and overwrites some key accelerators for integrate them with Sugar. 
Keep this in mind when setting up key accelerators in your activity.
At your convenience, edit files sugar/sweetener/stock.py and desktop/sweetener/stock.py.

{| class="wikitable"
|-
! '''Stock label''' !! '''Key accelerator on Sugar''' !! '''Key accelerator on Linux desktops'''
|-
| Add || Ctrl + A || Ctrl + A
|-
| Fullscreen || Alt + Return || F11
|-
| Normal Size || Ctrl + 0 || Ctrl + 0
|-
| Remove || Shift + Del || Ctrl + R
|-
| Save as || Unused :) || Ctrl + Shift + S
|-
| Select Color || Ctrl + L || Ctrl + L
|-
| Zoom In || Ctrl + + || Ctrl + +
|-
| Zoom Out || Ctrl + - || Ctrl + -
|}

== Activities using Sweetener==
* [[Activities/Graph_Plotter|Graph Plotter]]
* [http://git.sugarlabs.org/illustrate-sugar-integration/illustrate-sweetener Illustrate Sweetener] (Development)

== Gtk2 and Gtk3 Support ==
There are efforts to port Sweetener to Gtk3[http://git.sugarlabs.org/sudoku/mainline], but at the moment it isn't possible thanks to the upstream bug [https://bugzilla.gnome.org/show_bug.cgi?id=652697 GNOME#652697].