359
edits
Changes
Karma:Meeting 21 December 2009 (view source)
Revision as of 06:22, 21 December 2009
, 06:22, 21 December 2009no edit summary
Agenda
Agenda
# Coding Style
# Coding Style
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"
# common HTML mistakes
# common HTML mistakes
# Let's try to use a common js coding pattern
# Let's try to use a common js coding pattern
3) method calls
3) method calls
Unobtrusive JavaScript
Unobtrusive JavaScript -- let's try to stick to it
# common js problems, no blocks around ifs, ' ' eval, ==, var methodName = function(){}
# common js problems, no blocks around ifs, ' ' eval, ==, var methodName = function(){}
# managing code for lessons in repos, versioning
# managing code for lessons in repos, versioning
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_"
# Using draggable()?
# Using draggable()?
Vaibhaw will take look at jquery UI's draggable and see if useful
Vaibhaw will take look at jquery UI's draggable and see if useful
Bryan will look at dialog for help, playAgain
Bryan will look at dialog for help, playAgain
Bryan will add shuffle() to Karma
Bryan will add shuffle() to Karma
# timeline? milestones?
# timeline? milestones?
Vaibhaw will complete all 60 by March
Vaibhaw will complete all 60 by March
Bryan will check w/ Om to see if lesson dimensions will be part of UI design
Bryan will check w/ Om to see if lesson dimensions will be part of UI design
# Workflow - have Om review it?
# Workflow - have Om review it?
opyadav will review the finished activities