Changes

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

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

===Move an activity===

===Move an activity===

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_SugarLabs]] 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.

== Set up SugarLabs services ==

== Set up Sugar Labs services ==

* '''Upload a xo bundle''' to [http://activities.sugarlabs.org/ activities.sugarlabs.org].  Be sure to include a couple of screenshots of your activity in action.

* '''Upload a xo bundle''' to [http://activities.sugarlabs.org/ activities.sugarlabs.org].  Be sure to include a couple of screenshots of your activity in action.

* If your activity is part of Fructose, '''upload a .tar.bz2''' to [http://download.sugarlabs.org/ download.sugarlabs.org].  Request a shell account from the [[Infrastructure Team]] if you don't have one already.

* If your activity is part of Fructose, '''upload a .tar.bz2''' to [http://download.sugarlabs.org/ download.sugarlabs.org].  Request a shell account from the [[Infrastructure Team]] if you don't have one already.

===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===

;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====

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.

== 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 ===