Confirm
59
edits
Changes
→Useful settings: introduced
8.) Restart Sunbird and observe the 'Hello World!' greeting.
=== Finding a bug to fix===
* Don't be afraid to ask for help!
=== Useful hacking tools ===
* [irc://irc.mozilla.org IRC] - Sunbird and Lightning hackers and reviewers like to hang out in the #calendar channel on irc.mozilla.org. They're usually more than happy to answer your questions if you get stuck on a part of a patch. '''Be patient''' when asking questions, though. Hackers have to sleep, eat, and work too, so it may take several hours before someone sees your question and responds.
* [http://lxr.mozilla.org/mozilla/ LXR] - Great for searching the mozilla codebase for examples, particular code lines, etc.
* [http://www.geocities.com/gekacheka/moz/tool/FileBugReport/index.html File Bug Report] extension adds "File Sunbird Bug Report" to Sunbird's tools menu. Opens new Calendar bug report page, filling the build-id field with Sunbird's userAgent id (not the browser's).
* [http://www.geocities.com/gekacheka/moz/tool/leakmon/index.html Leak Monitor] patched to be installable in Sunbird.
=== Useful settings ===
* You can receive [[http://developer.mozilla.org/en/docs/Setting_up_extension_development_environment more debug messages]] with some preference settings.
* You can work within directories rather than JAR files. This eliminates the need to rebuild the jar files after a debug cycle. To work within <tt>chrome/calendar.jar</tt> extract this file to <tt>chrome/calendar</tt> and change the file <tt>calendar.manifest</tt> to:
# Settings for working with a directory structure instead of calendar.jar
skin calendar classic/1.0 calendar/skin/classic/calendar/
content calendar calendar/content/calendar/
content branding calendar/content/branding/ xpcnativewrappers=yes
=== Other possibly useful links ===
