Karma: Difference between revisions

Line 71:

* [[Karma/Specifications|Karma Specifications]] (early draft)

* Source Code stored in http://git.sugarlabs.org/projects/karma

* ~~Working demos at http://karma.sugarlabs.org~~

* Version Control and repository management see

* Unit ~~tests~~ http://karma.sugarlabs.org/tests/

* Unit testing is required for the karma.js library but not for individual lessons http://karma.sugarlabs.org/tests/

* Project Documentation kept in the Sugar Labs wiki

* Coding conventions: Based on [http://www.dojotoolkit.org/developer/StyleGuide Dojo Style Guide]

** Use camel-case 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"

** Whenever possible, use jslint ~~and then teach the rest of us how~~

** counters should be prefixed with "num" or "count"

** Anything Doug Crockford advises in "JavaScript: The Good Parts"

** Whenever possible, use [http://www.jslint.com/ jslint]

* File naming conventions: lowercase letters, underscore instead of spaces (need to write more about it)

@@ Line 71: / Line 71: @@
 * [[Karma/Specifications|Karma Specifications]] (early draft)
 * Source Code stored in http://git.sugarlabs.org/projects/karma
-* Working demos at http://karma.sugarlabs.org
+* Version Control and repository management see
-* Unit tests http://karma.sugarlabs.org/tests/
+* Unit testing is required for the karma.js library but not for individual lessons http://karma.sugarlabs.org/tests/
 * Project Documentation kept in the Sugar Labs wiki
 * Coding conventions: Based on [http://www.dojotoolkit.org/developer/StyleGuide Dojo Style Guide]
 ** Use camel-case 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"
-** Whenever possible, use jslint and then teach the rest of us how
+** counters should be prefixed with "num" or "count"
-** Anything Doug Crockford advises in "JavaScript: The Good Parts"
+** Whenever possible, use [http://www.jslint.com/ jslint]
 * File naming conventions: lowercase letters, underscore instead of spaces  (need to write more about it)