1,007
edits
Labs/Ubiquity/Ubiquity 0.1 Development Tutorial: Difference between revisions
Labs/Ubiquity/Ubiquity 0.1 Development Tutorial (view source)
Revision as of 23:39, 29 August 2008
, 29 August 2008→Development
No edit summary |
|||
| Line 32: | Line 32: | ||
= Development = | = Development = | ||
The heart of the code can be found in the subdirectory: | The heart of the code can be found in the subdirectory: | ||
| Line 38: | Line 37: | ||
ubiquity/chrome/content/ | ubiquity/chrome/content/ | ||
Make sure you run the test suite before committing your changes: | |||
Note: There is no need for you to keep on rebuilding your Extension after the first time. The changes to the manage.py built Extension are updated whenever you save updates to the source files and restart Firefox. | |||
== Don't Forget to Test == | |||
Make sure you run the test suite before committing your changes. From the root directory of your checkout, run: | |||
python manage.py test | python manage.py test | ||
Another way to run the same test suite is by visiting this page: | |||
chrome://ubiquity/content/test.html | |||
Due to slight differences between running javascript code in xpcshell on the command line, and running it in an html page, a test occasionally will fail on the html page even though it succeeds on the command line. In that case, you can ignore the failure on the html page. | |||
== Keeping Up to Date == | == Keeping Up to Date == | ||
| Line 59: | Line 65: | ||
We use this Wiki [http://wiki.mozilla.org/index.php?Ubiquity] and Getsatisfaction [http://getsatisfaction.com/mozilla/products/mozilla_ubiquity] as places to get feature requests and bug reports. These feed into an internal Trac-based ticketing system [http://labs.toolness.com/trac/report/1]. | We use this Wiki [http://wiki.mozilla.org/index.php?Ubiquity] and Getsatisfaction [http://getsatisfaction.com/mozilla/products/mozilla_ubiquity] as places to get feature requests and bug reports. These feed into an internal Trac-based ticketing system [http://labs.toolness.com/trac/report/1]. | ||
Login to the Trac [http://labs.toolness.com/trac/report/1] using an OpenID account. Check out what needs to be done, add things appropriately, choose unassigned tickets and start hacking! | Login to the Trac [http://labs.toolness.com/trac/report/1] using an OpenID account. Look for unassigned tickets (these are the ones that say "New" in the status column as opposed to "Assigned"). Check out what needs to be done, add things appropriately, choose unassigned tickets and start hacking! | ||
== Submitting Patches == | == Submitting Patches == | ||