1
edit
Changes
m
== Week 9 – Bug Fixing =='''March 4 Guest: Mike Shaver'''
== Week 10 – XPCOM - Modular Development in Mozilla ==* '''TODO'''** Complete your 0.2 plan and update your project wiki page.** Blog about your 0.2 plans as well as any help you need from other students** Complete and add 1 new contribution to your personal list of contributions.
no edit summary
[[Image:osd600_winter2008.png|thumb|300px|Photo taken at the end of the year. Open Source FTW! From left to right: Radovan Nesic, Peter Evanoff, Peter Chan, Joseph Cresencia, Chris Tyler. Also we're missing one person: Samer Ziadeh. [http://peter.sykokillers.com/wp-content/uploads/2008/04/picture.jpg High Quality]]]
== Week 1 (Jan 8) Course introduction ==
== Week 6 – Developing the Browser ==
* Lab - [[Modifying the Browser Lab]] * '''TODO'''** Complete the [[Modifying the Browser Lab|lab]] and '''post a patch''' to your personal wiki page.** Look at the [http://developer.mozilla.org/devnews/index.php/2007/10/08/keeping-an-eye-on-blockers/ list of current FF3/Gecko1.9 blocker bugs] and '''CC yourself''' on three bugs that are related to your project, or that you find interesting.** Write a '''blog summary''' of our experience '''watching a user in bugzilla''' from last week** Write a '''blog summary''' updating your progress on your 0.1 release.** Make sure your project wiki page is up to date and matches your 0.1 release goals.** Start looking for opportunities to help other projects as part of your contrib mark. Each student should have a list of ways you can get involved on their project wiki page. == Week 7 – Extending the Browser Release 0.1 == ToDo: * '''Finish''' your 0.1, '''release it''' (via your project Wiki), and '''blog about it''' (with a link to the release on your project page).* Catch up on blogging.* '''Plan your 0.2'''.
== Break Week ==
== Week 8 – Extending the Browser II Toward 0.2 ==
== Week 11 9 – XPCOM II - Using XPCOM from JS/Chrome Extending the Browser ==
* [http://developer.mozilla.org/en/docs/Extensions Firefox Extensions]** [http://developer.mozilla.org/en/docs/Setting_up_extension_development_environment Setting-up your development environment]** [http://developer.mozilla.org/en/docs/Building_an_Extension 'Hello World!' Extension Tutorial]* Lab - [[Dive into Mozilla Modifying Firefox using an Extension Lab|Modifying the Browser Part II - writing an extension]] * '''Readings/Resources'''** Video: [http://www.vimeo.com/395422 Best practices & design patterns for add-ons] by Mike Beltzner** Video: ** MozDev documentation on Extensions: http://developer.mozilla.org/en/docs/Extensions** Personal HOWTO for creating an extension: http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/ * '''TODO'''** Complete the [[Dive into Mozilla Modifying Firefox using an Extension Lab|lab]] and '''post the .xpi''' to your personal wiki page.** Blog about your experience writing your first extension. What was hard? What did you find confusing?** Complete your 0.1 release and write a '''blog post''' about what you've created, how to use it, and where to give feedback == Week 10 – 0.2 == ToDo:* Release your 0.2, update the project wiki page, and blog about it Ben Hearsum visit -- Thursday == Week 11 – Bug Fixing == * Finding a bug, filing, fixing, patching* Code Review, [http://www.mozilla.org/owners.html Module Owners and Peers]* Using '''CVS Log''' and '''Bonsai''' to determine who should review* Good Examples of Bugs** [https://bugzilla.mozilla.org/show_bug.cgi?id=343416 Bug 343416]** [https://bugzilla.mozilla.org/show_bug.cgi?id=335878 Bug 335878]** [https://bugzilla.mozilla.org/show_bug.cgi?id=132183 Bug 132183]* Lab - [[Thunderbird Bug Fix Lab|Fixing a bug in Thunderbird]] * '''Readings/Resources'''** [http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree Getting your patch in the tree]** [http://weblogs.mozillazine.org/lilmatt/2007/05/it_begins.html Personal blog account of fixing a bug]** [http://fdiv.net/2007/05/15/the-secret-life-of-a-thunderbird-patch/#more-74 Personal blog account of fixing a bug in Thunderbird] * '''TODO'''** Complete this week's [[Thunderbird Bug Fix Lab|lab]] (hopefully during class time). Make sure you complete the '''Wiki''' and '''Blog''' requirements in the lab. == Week 12 – Major Project Presentations XPCOM ==* Intro to [http://developer.mozilla.org/en/docs/XPCOM XPCOM]** XPCOM can be built in C++ or [http://developer.mozilla.org/en/docs/How_to_Build_an_XPCOM_Component_in_Javascript using JS]** Components, [http://developer.mozilla.org/en/docs/Interfaces Interfaces], and [http://developer.mozilla.org/en/docs/XPIDL XPIDL]* Optional Lab: [[Real World Mozilla First XPCOM Component|Creating a Binary C++ XPCOM Component]]. * '''Readings/Resources'''** [http://sparc.senecacollege.ca/pub/mozilla.lecture/mozilla-20073/bsmedberg-xpcom-seneca.avi Introduction to XPCOM] (on-line lecture) by Mozilla's Benjamin Smedberg** [http://developer.mozilla.org/en/docs/Creating_XPCOM_Components "Creating XPCOM Components"] -- an excellent on-line book working step-by-step through creating a real XPCOM component.** [http://ted.mielczarek.org/code/mozilla/jscomponentwiz/ JS Component Wizard] * [http://sparc.senecacollege.ca/pub/mozilla.lecture/mozilla-20073/bsmedberg-xpcom-seneca.avi Ben Smedberg on XPCOM]. * TODO** Prepare your 0.3 release
== Week 13 – Presentations / Major Project Due ==
* Complete this week's [[Real World Mozilla First XPCOM Component|lab]], put a '''zip''' with all your files on your personal wiki page when done, and blog about the experience.
* Prepare for a brief (10-20 minute) demo on Thursday.
* Catch up on your blogging!
== Previous Versions of OSD600 ==
[[Fall 2007 Weekly Schedule]]
