Difference between revisions of "Implementing the Mouse Lock API in Firefox"

From CDOT Wiki
Jump to: navigation, search
(Created page with '==Introduction== This is a working document for the implementation of the [http://dvcs.w3.org/hg/webevents/raw-file/default/mouse-lock.htmlMouse Lock API spec] in Mozilla by stu…')
 
Line 14: Line 14:
 
* In class discussions: 11:40-1:30 Tuesday and Thursday in TEL T2110
 
* In class discussions: 11:40-1:30 Tuesday and Thursday in TEL T2110
 
* IRC discussions: [irc://irc.mozilla.org/seneca #seneca], [irc://irc.mozilla.org/paladin #paladin]
 
* IRC discussions: [irc://irc.mozilla.org/seneca #seneca], [irc://irc.mozilla.org/paladin #paladin]
* Questions: ...
+
* Questions: ask and answer any questions here: [[Mouse Lock Implementation FAQ]]
 
*  
 
*  
  
Line 24: Line 24:
 
# Break the spec down into an itemized list of things we need to do, tests we need to write, features we have to add, edge cases we have to worry about, demos we need to build, etc.  Put the info into this page.  We need to know everything we'll have to write and schedule when we'll do each bit.
 
# Break the spec down into an itemized list of things we need to do, tests we need to write, features we have to add, edge cases we have to worry about, demos we need to build, etc.  Put the info into this page.  We need to know everything we'll have to write and schedule when we'll do each bit.
 
# Blog about your work on this implementation
 
# Blog about your work on this implementation
# Add questions/answers to ...
+
# Add questions/answers to [[Mouse Lock Implementation FAQ]]
  
 
==Resources==
 
==Resources==

Revision as of 14:02, 31 October 2011

Introduction

This is a working document for the implementation of the Lock API spec in Mozilla by students in David Humphrey's Mozilla Development class at Seneca College.

Participants

  • David Humphrey (lead developer, professor, @humphd)
  • <your name here>

Communication

Development work will be done using a combination of the following:

Tasks

  1. Clone our repo and build a debug version locally
  2. Get a https://bugzilla.mozilla.org account and CC yourself on the bug.
  3. Set a Watch on this page and the Q/A page so you know when things change.
  4. Break the spec down into an itemized list of things we need to do, tests we need to write, features we have to add, edge cases we have to worry about, demos we need to build, etc. Put the info into this page. We need to know everything we'll have to write and schedule when we'll do each bit.
  5. Blog about your work on this implementation
  6. Add questions/answers to Mouse Lock Implementation FAQ

Resources