Jump to: navigation, search


1,556 bytes added, 01:31, 19 December 2016
GSoC Meetings
== The Karma Project ==
Karma is a framework for creating educational software using JavaScript, html5, and SVG. The Karma team is primarily focused on developing Sugar activities but you can also Karma to create lessons that run in any web browser that supports html5. The best ways to get involved are to join the [ mailing list] and [ get the code]
=== Rationale ===
=== Status ===
Karma is a sub-project of Sugar Labs that is under active development as a part of a [[Karma#GSoC_Project| Google Summer of Code project]]. The latest examples can be seen at []. 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 (yum install pywebkitgtk WebKit-gtk gnome-python2-gconf).
The current focus of development is to convert Nepal's set of lessons coded in Squeak smalltalk. You can find the list of lessons to be converted [ here]. This is a good place for new contributors to get started
=== What Karma Is ===
=== What Karma Isn't ===
* Karma is not compatible with Internet Explorer because Internet Explorer does not support html5 apis such as canvas, svg, localStorage, etc.
* 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
* Unobtrusive JavaScript
* No globals
* No extension of native objects extension
=== Technical Architecture ===
* Run-time - Karma will work with basic functionality on any W3C standards-compliant browser that supports HTML5 tags canvas , audio, and audiosvg. This notably excludes Microsoft's Internet Explorer. Karma will be particularly tailored to work within with Sugar's [[Browse]] activityJournal and collaboration through Telepathy. Longer-term we hope to extend Karma to take advantage of Sugar's collaboration features.* Primary Programming language - Javascript ([ New_in_JavaScript_1.6 Javascript 1.8.16]) Karma depends heavily the javascript library jQuery, version 1.3.
* [[Karma/i18n|i18n]] -- Pervasive internationalization is a critical part of Karma
** Supported types of i18n -- ToDo
*** Output of Native Digits
*** Image switching per locale
* Moodle Integration -- method to be determined
* [[Karma/Bundle_layout|Repo and Bundle layout]]
* UI Widgets
** [[Scoreboard]]
** Dialog -- use standard jQuery UI one?
=== Conventions ===
* The [[Karma/Dictionary|Karma Dictionary]]
* [[Karma/Specifications|Karma Specifications]] (early draft)
* [[Karma/Anti-conventions|Anti-Conventions]] -- coding no-nos* [[Karma/Layout_Converted_Squeak_Lessons|Layout for converted Squeak Lessons]]* Source Code stored in* Working demos at Each lesson must be in a folder named according to the schema "karma_Grade_Maths_title_WeekNo" where the week number is optional The following are valid names karma_3_Maths_LargestNumber_15 karma_2_English_MatchingPuzzle karma_6_Maths_AddingUpTo10_4* Version Control and repository management see the [[Karma#Version_Control|Version Control]] section of this page* Unit testing is required for the karma.js library but not for individual lessons
* Project Documentation kept in the Sugar Labs wiki
* Coding conventions: Based in on [ GNU standardsStyleGuide Dojo Style Guide] ** Use camel-case sadCamelCase for function names and variables
** Exception to above -- object constructors should start with a capital letter
** Set column-width to 79 characters (from Python standard practice)boolean variables should be prefixed with "is", "has", "can", or "should"** counters should be prefixed with "num" or "count"** Whenever possible, use [http://www.jslint and then teach the rest of us how** Anything Doug Crockford advises in "JavaScript: The Good Parts".com/ jslint]
* File naming conventions: lowercase letters, underscore instead of spaces (need to write more about it)
* Coding Pattern - We generally try to follow this coding pattern as it makes it easier to browse your code
Put code in following order
1) variable declarations
2) method declarations
3) method calls
== Version Control ==
Currently all lessons are stored in the examples/ folder of [ main karma repository]
== GSoC Project ==<strike>Here is how you can use the karma_lesson template to create a new repository from scratch  $ git clone git:// $ mkdir ../karma_3_English_3 # create a new lesson directory following our naming convention $ cp -r * ../karma_3_English_3 $ cd ../karma_3_English_3 $ rm -r .git # make sure you get rid of the old git directory $ git init $ git add . $ git commit -a -m "first commit"
=== Team === Now go to the, make sure you are logged inCreate a new project, use the same name as you did for your lesson's main folderthen, $ git remote add origin git://... # the pubic push url
Felipe Lopez Toledo "SubZero" is creating a prototype for Karma as a Google Summer of Code project. [[USER:BryanWB| Bryan Berry]] is serving as his mentor. [[User:ChristophD| Christoph Derndorfer]] is working Then on the draft coding your lesson ;)
=== [[KarmaFrom then on $ git push origin master # will sync your local tree w/To-Do|To-Do]] ===the server
=== Project Requirements ==='''Tagging''' -- a karma lesson can be in only one of two states, stable or unstable. Any commit tagged 'stable' is the stable version of your code. Every other version of your code is unstable. We will not use numeric versioning such as 0.1, 1.0, 1.2, etc. for the foreseeable future.</strike>
* 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]. == Meetings ==* This prototype should have the following features:** Simple interactive animation and audio using html5 tags like <canvas> and <audio>** An [[Karma/Assessment| assessment:Meeting 21 December 2009]] 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]** Some element of collaboration using Telepathy (This could be really hard, depending on the state of javascript bindings to dbus)
=== Meetings =GSoC Project ==
# Regular meeting between Felpe Karma started as a GSoC project with Felipe Lopez Toledo "SubZero" as the student participant and [[USER:BryanWB| Bryan every Tuesday 0215 UTC at #sugar on ircBerry]] as General GSOC meeting for participants from Sugar every Tuesday 1400 UTC #sugar-meeting
Meeting === GSoC Meetings === Notesfrom GSoC meetings - kept for archival purposes
* [[Karma:Meeting 12 May 2009]]
* [[Karma:Meeting 02 Jun 2009]]
* [[Karma:Meeting 08 Sep 2009]]
* [[Karma:Meeting 14 Sep 2009]]
* [[Karma:Meeting 21 Sep 2009]]
* [[Karma:Meeting 21 December 2009]]
==Project Roadmap = Roadmaps === ==== Subzero's University Thesis ==== Deadline: February  Goals: i18n mechanism, animation support, several good examples, final paper done* i18n mechanism: i18n on Karma Objects, inline html i18n, html2po tool* animation support: fps support, KGraphics events supportThese milestones are logged on [ Launchpad]
==== 0.1 "Osito" ====
Due Was completed September 11, 2009
* 1 Working example in "adding_up_to_10"
==== 0.2 "Gatito" ====
Due October 21, Completed mid-December 2009
This release is timed * unit testing added to coincide karma.js using QUnit* API documented w/ jsdoc-toolkit* support for SVG and canvas animation * 3 working examples** Adding_Up_to_10 using both SVG and canvas** Quadrilaterals ** "Conozco A Uruguay" done with Bryan's visit to Google HQ for the GSoC Mentor's Summitkarma -- 50% done
* 3 working examples
* animation support with k.timeline
* basic SVG support
* basic i18n support for inline text
* narwhal utility scripts
** jsdocs
** lesson2po
* separate plugin for i18n, perhaps called k4a or karma-for-all
==== 0.4 "niño" ====
Due 31 January 2010==== 0.3 "niño" ====
This release will be for Subzero's senior thesisDue 31 March 2010
* Full i18n support
* support for SVG and canvas animationAll Squeak lessons converted to Karma* fully functional "kpages"Integrate all of the existing E-Paath lesson into chakra * narwhal build scripts for chakra* scripts that automate creating script to build one giant karma bundle w/ all the E-Paath lessons as launchpad projects, like [ Quickly] does inside it and chakra
* At least 6 lessons ready that have been translated into 3 languages each
* Version 0.1 draft of karma specification done
==== 1.0 "Muchacho" Future Direction of Karma ====
This release may also be called "Karma 1000" and is a big wishlistNo schedule yet.
* Full moodle integration* Offline storage and synchronization with moodle* Integration with the Sugar Journal* Integration with Telepathy on Sugar[[Karma/Future Direction|This page]] has more information.
=== Library ===
* Differences between html4 and html5
* [ Dive Into HTML5]
General Web Design
* The [ SVG Primer] a very detailed and in-depth resource
* [ Raphaeljs documentation]
* [ Eloquent Javascript] best beginning javascript resource
* "Javascript: The Good Parts" book by Doug Crockford
* "jQuery in Action" book
Coding Tools and Conventions
* Venkman -- javascript debugger
* Firebug ---
* Web-Inspector --- webkit's answer to firebug
* Browsers --- We primarily work with Chromium and Firefox > 3.5
* For emacs users -- nxhtml mode and magit.el for working w/ git
* [ jslint]
* [ inkscape]
* [ narwhal]
== Subpages ==

Navigation menu