The Karma Project
Anyone with a modern standards-compliant web browser and a text editor should be able to create learning activities that can be used by anyone with a computer. Sugar should not be a walled garden that only allows learning activities expressly designed for it and it alone but rather gives extra power and depth to learning activities. Karma uses a specialized vocabulary that features a number of specialized terms. Please refer to the Karma Dictionary early and often.
Karma is a sub-project of Sugar Labs that is under active development as a part of a Google Summer of Code project. The latest examples can be seen at http://karma.sugarlabs.org. You can also check out the Karma Project blog for updates.
To try out the karma examples you need to have an html5-capable browser. The Browse activity within Sugar does not currently support html5. To try out karma within Sugar you need to install Surf and its webkit dependencies or run Firefox 3.5 from the command-line.
What Karma Is
- Karma is a simple framework to create simple interactive learning activities primarily for Sugar but also to be viewable through any web browser that supports html5
- Karma is used to create simple activities that run off-line w/out access to the Internet
- Karma is for web developers who want to contribute to Sugar using their current skills
- Karma is built to run on top of web browsers that support html5, particularly the canvas element.
- Karma is built around the concept of individual "lessons" and multiple lessons can be aggregated into a sugar activity
- Karma is the evolution of OLE Nepal's work on the EPaath suite of lessons in Nepal
- Karma is designed with pervasive and easy internationalizaton in mind and integration with moodle, particularly for monitoring student progress
- Karma is pedagogically agnostic. Pedagogical choices are left to the lesson author.
What Karma Isn't
- Karma is not meant to replace pyGTK as the dominant toolset for creating Sugar activities
- Karma is not a tool for creating activities with complex 3D graphics. Karma is a tool for creating activities with simple 2D graphics
- Karma is not meant as a basis for a WYSIWG programming environment like TurtleArt, EToys, or Logo
- Karma is not built to support browsers that do not support html5, such as Internet Explorer and Firefox < version 3.5
- Karma is not intended to teach programming to children though it could be used as such
- No globals
- No native objects extension
- Run-time - Karma will work with basic functionality on any W3C standards-compliant browser that supports HTML5 tags canvas and audio. This notably excludes Microsoft's Internet Explorer. Karma will be particularly tailored to work within Sugar's Browse activity. Longer-term we hope to extend Karma to take advantage of Sugar's collaboration features.
- i18n -- Pervasive internationalization is a critical part of Karma
- Supported types of i18n
- Output of Native Digits
- Image switching per locale
- Regular text, though it is unclear how to support plural forms, grammar shifts, and gender
- Audio switching per locale
- Integration with pootle
- Supported types of i18n
- Journal, Telepathy Integration -- method to be determined, perhaps using html5's offline storage feature, some resources here and here
- Moodle Integration -- method to be determined
- Repo and Bundle layout
- Anatomy of a Karma Lesson
- The Karma Dictionary
- Karma Specifications (early draft)
- Source Code stored in http://git.sugarlabs.org/projects/karma
- Working demos at http://karma.sugarlabs.org
- Project Documentation kept in the Sugar Labs wiki
- Code naming conventions: Based in GNU standards
- File naming conventions: lowercase letters, underscore instead of spaces (need to write more about it)
- Create a single prototype activity which could be used as a template for sugarizing AJAX activities. The GSoC participant should not create her own activity but recreate an existing activity such as one of OLE Nepal's flash activities.
- This prototype should have the following features:
- Simple interactive animation and audio using html5 tags like <canvas> and <audio>
- An assessment section that stores results of student's progress and gives them suggestions on improvement. Assessment info should be persistent.
- Uses simple html for the activity lesson plan and teacher notes.
- Integrates with the Journal
- Navigation and Help elements, ideally reusing widgets from jQuery
- Regular meeting between Felpe and Bryan every Tuesday 0215 UTC at #sugar on irc.freenode.net
- General GSOC meeting for participants from Sugar every Tuesday 1400 UTC #sugar-meeting
- Karma:Meeting 12 May 2009
- Karma:Meeting 02 Jun 2009
- Karma:Meeting 09 Jun 2009
- Karma:Meeting 23 Jun 2009
- Karma:Meeting 30 Jun 2009
- Karma:Meeting 21 Jul 2009
- Karma:Meeting 4 Aug 2009
- Karma:Meeting 11 Aug 2009
Before GSoc - June 1:
- get familiar with Sugar
- get familiar with html5
- Felipe to acquire XO
- select the appropriate js framework -- jQuery
June 2 - June 12:
- “Karming” the "Quadrilaterals" activity using a non-elegant approach
- Post blog entry detailing challenges encountered and ideas on how to simplify the animation methods
- Post message to jquery-en and jquery-dev mailing lists asking for feedback
June 13 - July 12:
- Developing the first Karma widget (easy animation tool, boost animation tool from the selected js framework)
- Getting familiar with Sugar/Browse code
- Providing Karma + audio
- Providing Karma + client-side i18n
- Developing an activity template for Karma
- Changing the original activity to include above features
July 13: Publish blog post that showcases updated activity. Explain problems encountered, what works, what still doesn’t.
July 15 - July 25:
- Fixing bugs
- Work on gears+karma support
July 26 - July 31:
- Documenting examples
- Improving documentation
August 1 - August 9: time for any eventual emergencies
- It could be very difficult to interface titanium with telepathy. Risk Level: High