XULRunner Frequently Asked Questions. Work in progress.
Installing developer extensions
To be able to install any extensions, you first need to enable the Extension Manager in application.ini. Note that XULRunner, as of 126.96.36.199, does not appear to load extensions from the application directory; only the XULRunner directory and the user profile directory are checked.
- Need a custom build or a compatible extension <is there downloadable venkman/domi for 188.8.131.52?>
- Need to edit compatibility in install.rdf to match the id and versions in application.ini
- Needs a method to start venkman (usually by overlaying the main XUL file, similar to existing code for Firefox, Suite, etc.)
- anything else?
Same as venkman
Need custom build, first of all. What else?
Extension Developer's Extension
To install the extension into your application you'll need to hack its install.rdf (see above). You'll probably also want to create menuitems that let you open the JS Shell and other tools provided by the extension.
Branding is a chrome package containing product-specific information (e.g. the product name, vendor, and logo).
Some XULRunner components (in particular, the Extension Manager) depend on branding, in the sense that they expect to find certain strings in <tt>chrome://branding/locale/brand.dtd</tt> and <tt>chrome://branding/locale/brand.properties</tt>.
In order to satisfy these dependencies, you can save Firefox's <tt>brand.dtd</tt>/<tt>brand.properties</tt> to <tt>chrome/branding/locale</tt> folder, modify them appropriately, and register a locale provider for <tt>branding</tt> by adding the following line to your chrome manifest:
locale branding en-US chrome/locale/branding/
The location you put the branding files in doesn't matter, as long as you register it appropriately in the manifest.
In ''~.mozconfig'': ac_add_options --enable-branding=« branding location »
Reading command line arguments
See Chrome: Command Line. Command line arguments are handled via nsICommandLineHandler as usual.