Activity Team/Creating a New Activity - Revision history

Ignacio Rodríguez: /* Checklist for new activities */

2014-12-02T18:18:12Z

Checklist for new activities

← Older revision		Revision as of 14:18, 2 December 2014
Line 5:		Line 5:
	== Checklist for new activities ==		== Checklist for new activities ==

	* Create a ~~Gitorious~~ project repository at http://~~git~~.~~sugarlabs.org/~~ and start hacking on your code! :-)		* Create a GitHub project repository at http://github.com and start hacking on your code! :-)
	* Request a trac component for your activity at http://bugs.sugarlabs.org/		* Request a trac component for your activity at http://bugs.sugarlabs.org/
	* Open a trac ticket to request addition to http://translate.sugarlabs.org/ (when your strings are mature)		* Open a trac ticket to request addition to http://translate.sugarlabs.org/ (when your strings are mature)

Bernie: /* Activity authors' documentation */

2010-04-11T15:33:06Z

Activity authors' documentation

← Older revision		Revision as of 11:33, 11 April 2010
Line 1:		Line 1:
	== ~~Activity~~ authors~~' documentation~~ ==		== Documentation for activity authors ==

	See [[Activity Team/Resources]].		See [[Activity Team/Resources]].


	== Checklist for new activities ==		== Checklist for new activities ==

Bernie at 15:31, 11 April 2010

2010-04-11T15:31:52Z

← Older revision		Revision as of 11:31, 11 April 2010
Line 1:		Line 1:
	== ~~Developer~~ documentation ==		== Activity authors' documentation ==

	See [[Activity Team/~~Developer resources~~]].		See [[Activity Team/Resources]].

Bernie at 15:26, 11 April 2010

2010-04-11T15:26:16Z

← Older revision		Revision as of 11:26, 11 April 2010
Line 12:		Line 12:

	* If your Activity is migrating over from the OLPC infrastructure, see: [[Activity_Team/How_to_migrate_from_OLPC\|How to migrate from OLPC]].		* If your Activity is migrating over from the OLPC infrastructure, see: [[Activity_Team/How_to_migrate_from_OLPC\|How to migrate from OLPC]].

			== When releasing an existing Activity ==

			* If you have one, update your wiki page at http://wiki.sugarlabs.org/go/Activities/<actvity-name>
			* Upload your new .xo bundle, screenshots, notes to http://activities.sugarlabs.org/
			* Unless your source code is already available through git, upload a .bz2 source tarball to shell.sugarlabs.org /upload/sugar/sources/honey (e.g., scp to download.sugarlabs.org:/srv/upload/sources/fructose/...)
			* Edit http://wiki.sugarlabs.org/go/Development_Team/Source_Code and make sure it's pointing to your latest source tarball

	== Before you write a new activity ==		== Before you write a new activity ==

Bernie at 15:05, 11 April 2010

2010-04-11T15:05:38Z

← Older revision		Revision as of 11:05, 11 April 2010
Line 1:		Line 1:
	~~For new Activities:~~		== Developer documentation ==
	~~Create a Gitorious project repository at http://git.sugarlabs.org/ and start hacking on your code! :-)~~
	~~Request a trac component for your activity at http://dev.sugarlabs.org/~~
	~~Open a trac ticket to request addition to Pootle our translation system (if your strings are mature)~~
	~~Add your Activity to http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap if you want to be on the SoaS distro~~

	~~Do you have an idea for a new~~ Activity ~~you'd like to write but don't know how to begin? Here's some advice:~~		See [[Activity Team/Developer resources]].

	1). Don't try to write a Sugar Activity right away. Instead, write a standalone Python program that does what you want, then convert it to a Sugar Activity, being sure to keep a copy of the non-Sugarized version around for future use. There are several reasons for this, but the chief one is that standalone programs are easier to test, especially if you are not currently a Linux user. A standalone Python program can run anywhere, but a Sugar Activity really needs Sugar running on top of Linux. You can run your standalone Python program on an XO using the Terminal Activity.

	~~When I add~~ new features to my Sugar Activities I generally try to get the feature working on the standalone version first. I did this with text to speech in Read Etexts, for instance. This was useful because when I ran into problems I had a standalone app I could send to the speech-dispatcher mailing list so they could easily recreate my problem.		== Checklist for new activities ==

	2). ~~Sugar Activities are generally made with pygtk or pygame, and I believe pygtk is the more common of the two~~. ~~These~~ are ~~both cross platform and have online tutorials, as does Python itself~~:		* Create a Gitorious project repository at http://git.sugarlabs.org/ and start hacking on your code! :-)
			* Request a trac component for your activity at http://bugs.sugarlabs.org/
			* Open a trac ticket to request addition to http://translate.sugarlabs.org/ (when your strings are mature)
			* Add your Activity to http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap if you want to be on the SoaS distro

	* ~~http~~:/~~/www.python.org/~~		* If your Activity is migrating over from the OLPC infrastructure, see: [[Activity_Team/How_to_migrate_from_OLPC\|How to migrate from OLPC]].
	* http://www.pygtk.org/
	* http://www.pygame.org/news.~~html~~

	~~3). You'll want~~ a ~~good code-highlighting editor that understands Python. A couple of good ones:~~		== Before you write a new activity ==

	* Eric: ~~http://eric-ide.python-projects.org/eric4-download.html~~		Do you have an idea for a new Activity you'd like to write but don't know how to begin? Here's some advice:
	* Gedit: http://projects.gnome.org/gedit/

	~~These are~~ a ~~bit more complicated~~ to ~~install than typical Windows programs~~. ~~They~~ are ~~included in every~~ Linux ~~distribution~~, ~~though~~.		* Don't try to write a Sugar Activity right away. Instead, write a standalone Python program that does what you want, then convert it to a Sugar Activity, being sure to keep a copy of the non-Sugarized version around for future use. There are several reasons for this, but the chief one is that standalone programs are easier to test, especially if you are not currently a Linux user. A standalone Python program can run anywhere, but a Sugar Activity really needs Sugar running on top of Linux. You can run your standalone Python program on an XO using the Terminal Activity.

	~~4). To make and test a Sugarized Activity you really should have a Linux distribution installed. The best for this purpose is probably Fedora 10, which includes~~ the ~~Sugar environment, eric, gedit, python, pygame, pygtk, a tool for making SVG icons, and lots of other useful stuff. You can run Linux~~ on the ~~same computer as Windows XP (by partitioning your hard drive, something the Fedora installer will do for you) and choose which one you want to run at boot time~~. ~~Fedora 10 is no more difficult~~ to ~~install than Windows is, even if you want to run it and Windows on the same machine~~, ~~and will run on hardware that would be inadequate~~ for ~~current versions of Windows~~. ~~A Pentium III with 256 meg of RAM and~~ a ~~few gig of hard disk is more than adequate for Sugar development.~~		When I add new features to my Sugar Activities I generally try to get the feature working on the standalone version first. I did this with text to speech in Read Etexts, for instance. This was useful because when I ran into problems I had a standalone app I could send to the speech-dispatcher mailing list so they could easily recreate my problem.

	~~The Sugar environment that comes with Fedora 10 should be adequate for creating Activities. It is not~~ the ~~latest version of Sugar, but keep in mind that most XO laptops won't be running the latest Sugar either~~.

	~~If you don~~'t want ~~to have anything to do with Linux you ''could'' make~~ a ~~standalone~~ Python ~~program and find~~ a ~~collaborator~~ to ~~Sugarize it for you~~. ~~You could also attempt to develop your Activity using Sugar on a Stick, or an actual XO~~, ~~but this would probably be more trouble than simply installing Fedora 10~~.		* You'll want a good code-highlighting editor that understands Python. A couple of good ones:
			:* Eric: http://eric-ide.python-projects.org/eric4-download.html
			:* Gedit: http://projects.gnome.org/gedit/
			:These are a bit more complicated to install than typical Windows programs. They are included in every Linux distribution, though.

	5). ~~When~~ you ~~are ready~~ to ~~Sugarize your Python program~~, ~~read these articles:~~		* To make and test a Sugarized Activity you really should have a Linux distribution installed. The best for this purpose is probably Fedora, which includes the latest Sugar environment, eric, gedit, Python, pygame, PyGTK, a tool for making SVG icons, and lots of other useful stuff. You can run Linux on the same computer as Windows (by partitioning your hard drive, something the Fedora installer will do for you) and choose which one you want to run at boot time. Fedora is no more difficult to install than Windows is, even if you want to run it and Windows on the same machine, and will run on hardware that would be inadequate for current versions of Windows. A Pentium III with 256 meg of RAM and a few gig of hard disk is more than adequate for Sugar development.

	* ~~http://wiki~~.~~sugarlabs~~.~~org/go/Development_Team/Almanac~~		* If you don't want to have anything to do with Linux, you ''could'' make a standalone Python program and find a collaborator to Sugarize it for you. You could also attempt to develop your Activity using Sugar on a Stick, or an actual XO, but this would probably be more trouble than simply installing Fedora 10.
	* http://wiki.laptop.org/go/Beyond_Hello_World

	Feel free to ignore any of this advice if it doesn't seem applicable. I hope that you'll find it gives you a place to start.		Feel free to ignore any of this advice if it doesn't seem applicable. I hope that you'll find it gives you a place to start.

Patrol: moved Walter is a wanker 10/Creating a New Activity to Activity Team/Creating a New Activity over redirect: revert

2010-02-24T01:43:30Z

moved Walter is a wanker 10/Creating a New Activity to Activity Team/Creating a New Activity over redirect: revert

← Older revision	Revision as of 21:43, 23 February 2010
(No difference)

Page move vandal: moved Activity Team/Creating a New Activity to Walter is a wanker 10/Creating a New Activity: Walter is a wanker

2010-02-24T00:20:04Z

moved Activity Team/Creating a New Activity to Walter is a wanker 10/Creating a New Activity: Walter is a wanker

← Older revision	Revision as of 20:20, 23 February 2010
(No difference)

Dfarning: update link

2009-08-30T19:43:19Z

update link

← Older revision		Revision as of 15:43, 30 August 2009
Line 37:		Line 37:
	Feel free to ignore any of this advice if it doesn't seem applicable. I hope that you'll find it gives you a place to start.		Feel free to ignore any of this advice if it doesn't seem applicable. I hope that you'll find it gives you a place to start.

	See also: [[Activity_Team/Resources]] , [[~~Modifying_Activities~~]] and [[Activities/Turtle_Art/Patching]]		See also: [[Activity_Team/Resources]] , [[Activity_Team/Modifing_an_Activity]] and [[Activities/Turtle_Art/Patching]]

	==Additional tips and common "gotchas"==		==Additional tips and common "gotchas"==

Dfarning: add content from james simmons page

2009-08-30T19:30:32Z

add content from james simmons page

@@ Line 5: / Line 5: @@
      Add your Activity to http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap if you want to be on the SoaS distro
-If your Activity is migrating over from the OLPC infrastructure:
+Do you have an idea for a new Activity you'd like to write but don't know how to begin?  Here's some advice:
-When releasing an existing Activity:
+).  Don't try to write a Sugar Activity right away.  Instead, write a standalone Python program that does what you want, then convert it to a Sugar Activity, being sure to keep a copy of the non-Sugarized version around for future use.  There are several reasons for this, but the chief one is that standalone programs are easier to test, especially if you are not currently a Linux user.  A standalone Python program can run anywhere, but a Sugar Activity really needs Sugar running on top of Linux.  You can run your standalone Python program on an XO using the Terminal Activity.
-    If you have one, update your wiki page at http://wiki.sugarlabs.org/go/Activities/<actvity-name>
-    Upload your new .xo bundle, screenshots, notes to http://activities.sugarlabs.org/
+When I add new features to my Sugar Activities I generally try to get the feature working on the standalone version first.  I did this with text to speech in Read Etexts, for instance.  This was useful because when I ran into problems I had a standalone app I could send to the speech-dispatcher mailing list so they could easily recreate my problem.
-    Upload .bz2 source to shell.sugarlabs.org /upload/sugar/sources/honey
-    Edit http://wiki.sugarlabs.org/go/Development_Team/Source_Code and make sure it's pointing to your latest .bz2
+).  Sugar Activities are generally made with pygtk or pygame, and I believe pygtk is the more common of the two.  These are both cross platform and have online tutorials, as does Python itself:

Dfarning: Add outline

2009-08-30T19:13:50Z

Add outline

← Older revision		Revision as of 15:13, 30 August 2009
Line 1:		Line 1:
	~~stub~~		For new Activities:
			Create a Gitorious project repository at http://git.sugarlabs.org/ and start hacking on your code! :-)
			Request a trac component for your activity at http://dev.sugarlabs.org/
			Open a trac ticket to request addition to Pootle our translation system (if your strings are mature)
			Add your Activity to http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap if you want to be on the SoaS distro

			If your Activity is migrating over from the OLPC infrastructure:
			See How to migrate from OLPC.

			When releasing an existing Activity:
			If you have one, update your wiki page at http://wiki.sugarlabs.org/go/Activities/<actvity-name>
			Upload your new .xo bundle, screenshots, notes to http://activities.sugarlabs.org/
			Upload .bz2 source to shell.sugarlabs.org /upload/sugar/sources/honey
			Edit http://wiki.sugarlabs.org/go/Development_Team/Source_Code and make sure it's pointing to your latest .bz2