10,505
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + − + + + + − + − Please see the [[Features/Soas_V4/ASLOxo_Activity_Test_Table|Activity Test-table page]] for tester information. − === Problems logging in to Gitorious? === − + − Fake emails to identify users:+ − * ''activity.team@sugarlabs.org'' activities that are supported by Activity Team+ − + + + + + + + + + + + + + + + + + + + + Line 24:
Line 46: + + − − ===setup.py=== − − There is a handy utility that is a standard part of Sugar Activity bundles, setup.py. You should use it to create and update POT files, generate a MANIFEST file and update locale files, and create .xo and .tar files for distribution. − − ./setup.py genpot − ./setup.py fix_manifest − ./setup.py dist_xo − ./setup.py dist_source − The [http://activities.sugarlabs.org Sugar Activity Library] is our new user-facing portal for Sugar activities. The site uses the backend Mozilla built for Firefox and Thunderbird extensions at addons.mozilla.org, called Remora. To help out, check out [[Activity Library]]. − + Line 51:
Line 65: + + + + + + + + + + + + + + + + + Line 58:
Line 89: − − ===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. − − 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. − − [[User:Wade|Wade]] 17:19, 13 January 2009 (UTC) Line 83:
Line 106: − + − − As Sugar is integrated into more distros and the hardware base expands, it is important to keep Activity developers informed of any issues they need be aware of. For example, when Sugar was only expected to run on the XO-1 laptop, it was safe to assume that the display was always 1200x900. − − The [[Activity Team/Compatibility Tips|Compatibility Tips]] page is a place to accumulate tips. − − − ===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. − − *[[Activity_Team/Modifying_an_Activity]] − ==== A typical update cycle ==== Line 110:
Line 122: − ===[[Activity Team/Project Ideas|Project Ideas]]=== +
reordering of page into slightly more coherent hierarchy
<noinclude><div class="noprint">{{TeamHeader|Activity Team}}</div></noinclude>
<noinclude><div class="noprint">{{TeamHeader|Activity Team}}</div></noinclude>
==Mission==
==Mission==
{{:Activity Team/Mission}}
{{:Activity Team/Mission}}
== Creating a new activity ==
==Tips for Activity Developers==
=== Creating a new activity ===
See [[Activity Team/Resources|Activity Team Resources]].
See [[Activity Team/Resources|Activity Team Resources]].
== Testers ==
=== Problems logging in to Gitorious? ===
Gitorious users are sometimes having their IP addresses incorrectly blacklisted by OSU-OSL, the organization that hosts git.sugarlabs.org. If your SSH key is rejected with the error "Access denied or bad repository path", please open a ticket by emailing support@ouosl.org.
Gitorious users are sometimes having their IP addresses incorrectly blacklisted by OSU-OSL, the organization that hosts git.sugarlabs.org. If your SSH key is rejected with the error "Access denied or bad repository path", please open a ticket by emailing support@ouosl.org.
This has happened to a number of activity authors and we are working on getting it resolved.
This has happened to a number of activity authors and we are working on getting it resolved.
=== Activity Team users on activities.sugarlabs.org ===
===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.
* ''trash@dev.null'' activities to remove
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===
As Sugar is integrated into more distros and the hardware base expands, it is important to keep Activity developers informed of any issues they need be aware of. For example, when Sugar was only expected to run on the XO-1 laptop, it was safe to assume that the display was always 1200x900.
The [[Activity Team/Compatibility Tips|Compatibility Tips]] page is a place to accumulate tips.
===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.
*[[Activity_Team/Modifying_an_Activity]]
== Testers ==
Please see the [[Features/Soas_V4/ASLOxo_Activity_Test_Table|Activity Test-table page]] for tester information.
== Background information ==
=== Sugar Activities ===
=== Sugar Activities ===
===Sugar [[Human Interface Guidelines]]===
===Sugar [[Human Interface Guidelines]]===
The [[Human_Interface_Guidelines|Sugar Human Interface Guidelines]] content has also been migrated to Sugar Labs. This guide is a critical resource when designing activities.
The [[Human_Interface_Guidelines|Sugar Human Interface Guidelines]] content has also been migrated to Sugar Labs. This guide is a critical resource when designing activities.
: An [[Activity Team/Project Ideas#Activity HIG|Activity HIG]] discussion
: An [[Activity Team/Project Ideas#Activity HIG|Activity HIG]] discussion
===Sugar Almanac===
===Sugar Almanac===
The [[Development Team/Almanac|Sugar Almanac]] content has been migrated to Sugar Labs. It's a great, quick reference when building python Activities.
The [[Development Team/Almanac|Sugar Almanac]] content has been migrated to Sugar Labs. It's a great, quick reference when building python Activities.
===activities.sugarlabs.org===
===activities.sugarlabs.org===
[[User:Wade|Wade]] 15:02, 27 January 2009 (UTC)
The [http://activities.sugarlabs.org Sugar Activity Library] is our user-facing portal for Sugar activities. The site uses the back-end Mozilla built for Firefox and Thunderbird extensions at addons.mozilla.org, called Remora. To help out, check out [[Activity Library]].
===sugar-widgets library===
===sugar-widgets library===
See [[Activity Team/Sugar-sprites]]
See [[Activity Team/Sugar-sprites]]
== Misc. ==
=== Activity Team users on activities.sugarlabs.org ===
Fake emails to identify users:
* ''activity.team@sugarlabs.org'' activities that are supported by Activity Team
* ''trash@dev.null'' activities to remove
===setup.py===
There is a handy utility that is a standard part of Sugar Activity bundles, setup.py. You should use it to create and update POT files, generate a MANIFEST file and update locale files, and create .xo and .tar files for distribution.
./setup.py genpot
./setup.py fix_manifest
./setup.py dist_xo
./setup.py dist_source
===Packaging activities discussion===
===Packaging activities discussion===
** should we remove "Activities" section from that page; all issues where moved to Activity_Status page [[User:Alsroot|alsroot]] 10:33, 16 January 2009 (UTC)
** should we remove "Activities" section from that page; all issues where moved to Activity_Status page [[User:Alsroot|alsroot]] 10:33, 16 January 2009 (UTC)
* [[Activity Team/Packaging Ideas|Packaging ideas]]
* [[Activity Team/Packaging Ideas|Packaging ideas]]
=== The Sugar Control Panel ===
=== The Sugar Control Panel ===
* [http://www.gitcasts.com/ Gitcasts]
* [http://www.gitcasts.com/ Gitcasts]
===Cross-platform compatibility===
=== 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:
Anyone can contribute a patch to a Sugar Activity. The typical work cycle involves an interaction with the activity (project) maintainer as follows:
# make a clone (anyone)
# make a clone (anyone)
# update wiki documentation (anyone)
# update wiki documentation (anyone)
==[[Activity Team/Project Ideas|Project Ideas]]==
The Activity Team always needs project ideas and suggestions. Post your ideas to [[Activity Team/Project Ideas]].
The Activity Team always needs project ideas and suggestions. Post your ideas to [[Activity Team/Project Ideas]].