With many thanks to Dave Townsend and Robert Strong for reviews, Mozilla trunk builds now support extensions for “the toolkit” – meaning any XULRunner app which uses the toolkit. This will also be true for the next milestone, and (barring something really unusual) Mozilla 1.9 and the next major XULRunner release.
I can think of several extensions which would be good candidates:
- Bug 342592 – DOM Inspector (FIXED)
- Bug 312970 – XForms
The bug for DOM Inspector has a pretty simple example of how you’d add support for the toolkit to an extension. It’s less than ten new lines, added to install.rdf.
There’s also a nice side benefit possible here: extensions for another application – say, Songbird – which don’t need to be for just that application could port easily over to Firefox with the toolkit target.
So what determines if an extension should be for “the toolkit”? First, you need module owner or author’s approval for that extension. 🙂 Second, it shouldn’t be specific to a given product or written for a given application – for instance, an extension for browser history doesn’t qualify. On the other hand, if it adds more tools (a new SQLite database, for example, or a spell-checking dictionary – thanks for the idea, KaiRo) or capabilities without requiring that the app be a browser, a mail client, a multimedia player, etc., then it should be fine.
I’d invite fellow developers to start experimenting with this, and generate feedback. Any bugs to add “the toolkit” as a supported application should be marked as depending on bug 299716. Also, any other missing support for toolkit extensions we need bugs on, depending on bug 299716. We need eyeballs!
P.S. Congratulations on document.elementFromPoint(x, y), Mr. Karel. That’s very useful, too.