Changes

==I.M.A.G.E.==

==I.M.A.G.E.==

If you are taking the time to write a Sugar activity or "sugarizing" some open-source software to run  in the Sugar environment, you will want to take some extra time to give it the best IMAGE you can.  The I.M.A.G.E. rubric does not represent the only factors that you should take into account when writing your activity, the Sugar Human Interace Guidelines represent a more complete discussion of design considerations.  IMAGE represents a few important factors that too often are overlooked that sometimes presents barriers to the wider use of a Sugar activity and therefore deserve to be pointed out specific atterntion.  

If you are taking the time to write a Sugar activity or "sugarizing" some open-source software to run  in the Sugar environment, you will want to take some extra time to give it the best IMAGE you can.  The I.M.A.G.E. rubric does not represent the only factors that you should take into account when writing your activity, the [http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines| Human Interace Guidelines] represent a more complete discussion of design considerations.  IMAGE represents a few important factors that too often are overlooked that sometimes presents barriers to the wider use of a Sugar activity and therefore deserve to be pointed out specific atterntion.  

===I is for Internationalization (I18n)===

===I is for Internationalization (I18n)===

===A is for Activity testing===

===A is for Activity testing===

Activity authors generally want feedback from testers on many different platforms and environments.  The best way to get your activity tested thoroughly is to provide some initial testing scripts that cover the primary or essential functions of the activity.  At present the best way to do this is to use the Semantic MediaWiki templates on the OLPC wiki that are being developed by the Community Activity Testing group. Drafting your own testing scripts is the best way to get useful feedback from as many testers as possible as Sugar evolves through multiple releases over time.  Writing these testing scripts while your activity is in early phases of the development process and the various key features are fresh in your mind will be much easier than trying to produce them later.

Activity authors generally want feedback from testers on many different platforms and environments.  The best way to get your activity tested thoroughly is to provide some initial testing scripts that cover the primary or essential functions of the activity.  At present the best way to do this is to use the Semantic MediaWiki templates on the OLPC wiki that are being developed by the [[http://wiki.laptop.org/go/Community_Testing| Community Activity Testing] group. Drafting your own testing scripts is the best way to get useful feedback from as many testers as possible as Sugar evolves through multiple releases over time.  Writing these testing scripts while your activity is in early phases of the development process and the various key features are fresh in your mind will be much easier than trying to produce them later.

===G is for Generalization===

===G is for Generalization===

===E is for Educational content===

===E is for Educational content===

Porting a first-person shooter like Doom to run in Sugar may be a fun trick, but it has realtively little redeeming social value.  Sugar is meant to be focused on learning, so writing an activity that has a strong learning element by itself is good, writing one that integrates with some additional learning content or lesson plan materials that can be packaged with it may be even better.

Porting a first-person shooter like [http://wiki.laptop.org/go/Doom| Doom] to run in Sugar may be a fun trick, but it has realtively little redeeming social value.  Sugar is meant to be focused on learning, so writing an activity that has a strong learning element by itself is good, writing one that integrates with some additional learning content or lesson plan materials that can be packaged with it may be even better.