XULRunner tips

  • Revision slug: XULRunner_tips
  • Revision title: XULRunner tips
  • Revision id: 109103
  • Created:
  • Creator: Niczar
  • Is current revision? No
  • Comment cmd line args

Revision Content

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 1.8.0.1, does not appear to load extensions from the application directory; only the XULRunner directory and the user profile directory are checked.

Venkman

  • Need a custom build or a compatible extension <is there downloadable domi for 1.8.0.1?>
  • 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?


DOM Inspector

Same as venkman

Component Viewer

Need custom build, first of all. What else?

Extension Developer's Extension

fix install.rdf

Branding

Branding is required to use inspector and some features of XULRunner.

In ~.mozconfig:

ac_add_options --enable-branding=« branding location »

What is the format of a branding? Could'nt find it anywhere!

Reading command line arguments

Can i have JavaScript errors / warnings directed to stdout instead of the jsconsole?

See #306263

This doesn't do anything (1.8.0.1):

xulrunner -app application.ini -console

This neither (1.8.0.1) in defaults/preferences/«application name».js:

pref("javascript.options.strict", true);
pref("javascript.options.showInConsole", true);
pref("browser.dom.window.dump.enabled", true);

Revision Source

<p>
XULRunner Frequently Asked Questions. Work in progress.
</p>
<h2 name="Installing_developer_extensions"> Installing developer extensions </h2>
<p>To be able to install any extensions, you first need to enable the Extension Manager in <a href="en/XUL_Application_Packaging#em">application.ini</a>.  Note that XULRunner, as of 1.8.0.1, does not appear to load extensions from the application directory; only the XULRunner directory and the user profile directory are checked.
</p>
<h3 name="Venkman"> <a href="en/Venkman">Venkman</a> </h3>
<ul><li>Need a custom build or a compatible extension &lt;is there downloadable domi for 1.8.0.1?&gt;
</li><li>Need to edit compatibility in <i>install.rdf</i> to match the id and versions in application.ini
</li><li>Needs a method to start venkman (usually by overlaying the main XUL file, similar to existing code for Firefox, Suite, etc.)
</li><li>anything else?
</li></ul>
<p><br>
</p>
<h3 name="DOM_Inspector"> <a href="en/DOM_Inspector">DOM Inspector</a> </h3>
<p>Same as venkman
</p>
<h3 name="Component_Viewer"> Component Viewer </h3>
<p>Need custom build, first of all. What else?
</p>
<h3 name="Extension_Developer.27s_Extension"> Extension Developer's Extension </h3>
<p>fix install.rdf
</p>
<h2 name="Branding"> Branding  </h2>
<p>Branding is required to use inspector and some features of XULRunner.
</p><p>In <i>~.mozconfig</i>:
</p>
<pre class="eval">ac_add_options --enable-branding=« branding location »
</pre>
<p>What is the format of a branding? Could'nt find it anywhere!
</p>
<h2 name="Reading_command_line_arguments"> Reading command line arguments </h2>
<h2 name="Can_i_have_JavaScript_errors_.2F_warnings_directed_to_stdout_instead_of_the_jsconsole.3F"> Can i have JavaScript errors / warnings directed to stdout instead of the jsconsole? </h2>
<p>See <a class="external" href="https://bugzilla.mozilla.org/show_bug.cgi?id=306263">#306263</a>
</p><p>This doesn't do anything (1.8.0.1):
</p>
<pre class="eval">xulrunner -app application.ini -console
</pre>
<p>This neither (1.8.0.1) in <i>defaults/preferences/«application name».js</i>:
</p>
<pre class="eval">pref("javascript.options.strict", true);
pref("javascript.options.showInConsole", true);
pref("browser.dom.window.dump.enabled", true);
</pre>
Revert to this revision