Karma:Meeting 21 December 2009

Agenda when in doubt, use camelCase constants in all CAPS, w/ _ separating multiple words --> COUNT_ERRORS = 10; boolean variables should be prefixed w/ "is" "can" or "should" prefix counters with "count" or "num" Put code in following order 1) variable declarations 2) method declarations 3) method calls
 * 1) Coding Style
 * 1) common HTML mistakes
 * 2) Let's try to use a common js coding pattern

Unobtrusive JavaScript -- let's try to stick to it  Bryan will create karma-lesson repo lessons will have two states "stable" or "unstable", the "stable" commit is tagged "stable" everything else is unstable will use repo-naming convention from E-Paath but prefixed w/ "karma_" Vaibhaw will take look at jquery UI's draggable and see if useful Bryan will look at dialog for help, playAgain Bryan will add shuffle to Karma Vaibhaw will complete all 60 by March Bryan will check w/ Om to see if lesson dimensions will be part of UI design opyadav will review the finished activities
 * 1) common js problems, no blocks around ifs, '  ' eval, ==, var methodName = function{}
 * 2) managing code for lessons in repos, versioning
 * 1) Using draggable?
 * 1) Create common widgets? Scorebox? timer? -- yes we need all of them
 * 1) timeline? milestones?
 * 1) We need resolution help! at least I do
 * 1) Workflow - have Om review it?