Changes

<noinclude><div class="noprint">{{TeamHeader|Activity Team}}</div></noinclude>

<noinclude><div class="noprint">{{TeamHeader|Activity Team}}</div></noinclude>

=== Ask your 'newbie' question on-line ===

=== Ask your 'newbie' question on-line ===

Join [http://en.wikipedia.org/wiki/IRC IRC] channel [irc://irc.freenode.net/sugar-newbies #sugar-newbies] (e.g. via [http://webchat.freenode.net/?randomnick=1&prompt=1&channels=sugar-newbies web client]) and ask your question about activity, or sugar core, development process. Also browse chat [http://meeting.sugarlabs.org/sugar-newbies logs].

Join [http://en.wikipedia.org/wiki/IRC IRC] channel [irc://irc.freenode.net/sugar #sugar] (e.g. via [http://webchat.freenode.net/?randomnick=1&prompt=1&channels=sugar web client]) and ask your question about activity, or sugar core, development process. Also browse chat [http://meeting.sugarlabs.org/sugar logs].

=== Creating a new activity ===

=== Creating a new activity ===

See [[Activity Team/Creating a New Activity|Creating a New Activity]] and [[Activity Team/Resources|Activity Team Resources]].

See [[Activity Team/Creating a New Activity|Creating a New Activity]] and [[Activity Team/Resources|Activity Team Resources]].

=== Problems logging in to Gitorious? ===

=== Automated Testing ===

 

 

===Port to GTK3===

Gitorious users are sometimes having their IP addresses incorrectly blacklisted at http://git.sugarlabs.org/.  If your SSH key is rejected with the error "Access denied or bad repository path", please open a ticket by emailing git AT sugarlabs DOT org.

We have hints on [[Features/GTK3/Porting|porting from GTK2 to GTK3]].

===Move an activity===

===Move an activity===

We need help moving activities over to Sugar Labs from OLPC's servers.  This is a great way to get started helping out the Activity Team.  See [[Activity Team/How_to_migrate_from_OLPC]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.

We need help moving activities over to Sugar Labs from GitHub servers.  This is a great way to get started helping out the Activity Team.  See [[Activity Team/How to migrate from Gitorious]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.

While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct.  This will really help out the distro packagers.

While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct.  This will really help out the distro packagers.

===Cross-platform compatibility===

===Cross-platform compatibility===

===Migrating from GTK2 to GTK3===

===Migrating from GTK2 to GTK3===

The Sugar platform is migrating from GTK2 to GTK3 to stay relevant with upstream changes and benefit from their efforts. Sugar 0.96 (available in OLPC 12.1 development builds) includes support for a transition period, where both GTK2 and GTK3 activities can coexists, but new Sugar features will only be added to the GTK3 toolkit (e.g. improvements in touchscreen support). Have a read through the [http://wiki.sugarlabs.org/go/Features/GTK3/Porting migration notes], and the [http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html GTK3 Python tutorials] to get a feel for how things need to be changed. New activities should be developed with GTK3, unless you need to support an existing deployment today using an older build.

The Sugar platform is migrating from GTK2 to GTK3 to stay relevant with upstream changes and benefit from their efforts. Sugar 0.96 (available in OLPC 12.1 development builds) includes support for a transition period, where both GTK2 and GTK3 activities can coexists, but new Sugar features will only be added to the GTK3 toolkit (e.g., improvements in touchscreen support). Have a read through the [[Features/GTK3/Porting|migration notes]], and the [http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html GTK3 Python tutorials] to get a feel for how things need to be changed. New activities should be developed with GTK3, unless you need to support an existing deployment today using an older build.

===Modify Activities===

===Modify Activities===

A guide has been  written describing how to make simple modifications to popular Sugar  activities.  Examples include adding sounds to TamTam, blocks to  TurtleArt, buttons to Calculate, etc.

A guide has been  written describing how to make simple modifications to popular Sugar  activities.  Examples include adding sounds to TamTam, blocks to  TurtleArt, buttons to Calculate, etc.

*[[Activity_Team/Modifying_an_Activity]]

* [[Activity Team/Modifying an Activity]]

 

 

===Internationalization===

===Internationalization===

# do a <code>git pull</code> to get a local copy of the .po files

# do a <code>git pull</code> to get a local copy of the .po files

# run <code>setup.py fix_manifest</code> to create the .mo files used at run time

# run <code>setup.py fix_manifest</code> to create the .mo files used at run time

Details can be found on the

Details can be found on the [[Translation Team/i18n Best Practices]] page.

*[[Translation_Team/i18n_Best_Practices]].

===General overview of git===

===General overview of git===

Read the brief overview below but then '''start''' with our  

Read the brief overview below but then '''start''' with our  

*[[Activity Team/Git Tutorial|git tutorial]].

* [[Activity Team/Git Tutorial|git tutorial]].

====glossary====

====glossary====

;gitorious: software for hosting git repositories, including a web interface for administration

;gitorious: software for hosting git repositories, including a web interface for administration

;git.sugarlabs.org: server hosted by Sugar Labs running gitorious

;git.sugarlabs.org: server hosted by Sugar Labs running gitorious

====Setup====

====Setup====

(Once per machine you're working on)

(Once per machine you're working on)

  git clone git://git.sugarlabs.org/whatever/mainline.git whatever

  git clone git://github.com/whatever/mainline.git whatever

====Regular usage====

====Regular usage====

So if you ever mess up and don't know how to fix it yourself, please

So if you ever mess up and don't know how to fix it yourself, please

stop (at least for me that's usually the hardest part ;) ), try to

stop (at least for me that's usually the hardest part ;) ), try to

recollect the exact sequence of actions (e.g. from shell history) and ask

recollect the exact sequence of actions (e.g., from shell history) and ask

for help.

for help.

== Maintainers ==

== Maintainers ==

Please see [[File:How_to_become_a_maintainer.pdf]] for an overview of the Activity maintenance process.

{{:Activity Team/Maintainers}}

== Testers ==

== Testers ==

Please see the  [[Features/Soas_V4/ASLOxo_Activity_Test_Table|Activity Test-table page]] for tester information.

Please see the  [[Testing/Activity Test Table]] for tester information.

== Background information ==

== Background information ==

===Mime types and file suffixes===

===Mime types and file suffixes===

You can associate your activity with mime types by including a mime_types entry in the activity/activity.info file; e.g.

You can associate your activity with mime types by including a mime_types entry in the activity/activity.info file; e.g.,

  mime_types = text/plain;text/x-python;text/x-logo;text/x-svg;application/xml;text/html;text/xml;image/svg+xml

  mime_types = text/plain;text/x-python;text/x-logo;text/x-svg;application/xml;text/html;text/xml;image/svg+xml

=== A typical update cycle ===

=== A typical update cycle ===

Anyone can contribute a patch to a Sugar Activity. The typical work cycle involves an interaction with the activity (project) maintainer as follows:

Moved to https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#modifying-activities

# upload .tar to download.sugarlabs.org (project maintainer)

# upload .xo to activities.sugarlabs.org (project maintainer)

=== OLPC XO game buttons ===

=== OLPC XO game buttons ===