Writing a Mozilla Application with XUL and Javascript
  Chrome structure [ << Previous | Next >> ]

  • XUL UIs are commonly referred to as ``chrome''.
  • The chrome directory is structured as follows...
    • content XUL files describing the UI, and JS files
    • skin CSS files
    • locale directories containing localized strings
      • en-US, en-GB, da-DK, etc. DTD files and .properties files for the locale (string bundles)
  • Chrome:// URLs have the following ``magic'' properties...
    • chrome://content/chatzilla resolves to <chrome-directory>/packages/chatzilla/chatzilla/content/chatzilla.xul
    • chrome://skin/chatzilla resolves to <chrome-directory>/packages/chatzilla/chatzilla/skin/chatzilla.css
    • chrome://locale/chatzilla/chatzilla.dtd resolves to <chrome-directory>/packages/chatzilla/chatzilla/locale/<current-locale>/chatzilla.dtd
  • Chrome needs to be installed before chrome:// urls will work

[ Presentation Overview | Agenda | XUL Documents | Summary of XUL Elements | XUL Document Example | XUL Document Screenshot | XUL Overlays | XUL Overlay Example | XUL Overlay Screenshot | RDF Data | RDF Graph Illustration | RDF and XUL Templates | XUL Template Example | XUL Template Example, Points of Interest | Conclusions | Extra Slides | RDF Data Sources | XPCOM and XPConnect | XPConnect Objects | Instantiating an XPCOM Component | Chrome structure | Installing Chrome | Sample manifest.rdf ]