===== chrome/ =====

==== JAR files ====

For JAR files, Mozilla requires the contents of content/, locale/language_code/ and skin/ to be displaced by an extra subdirectory named after the package.  For example, without a JAR file, you could have this layout in Mozilla's chrome directory:

  chrome/evergreen/content/main.xul

but if this were a JAR file:

  chrome/evergreen.jar

Then the contents of the jar file would have to look like this:

  chrome/content/evergreen/main.xul

In the both cases, the XUL file would be referenced by the chrome URL:

  chrome://evergreen/content/main.xul

==== Files ====

^ File ^ Description ^ Repository ^
| [[mozilla-devel:chrome:content:evergreen|content/evergreen/]] | This is where the XUL and Javascript go. | [[http://open-ils.org/cgi-bin/viewcvs.cgi/ILS/Evergreen/staff_client/chrome/content/evergreen/|CVS]] |
| [[mozilla-devel:chrome:locale:en-US:evergreen|locale/en-US/evergreen/]] | DTD and .properties files for localization.  Chrome URL's get magical with locale depending on the framework's locale.  For example, I reference **chrome://evergreen/locale/auth.dtd** in one file, but it gets interpreted as **locale/en-US/auth.dtd** because that is my browser's locale.   Property files are used for localizing the text used in scripts.  There is a XUL element called a **stringbundle** ([[http://www.xulplanet.com/references/elemref/ref_stringbundle.html|Info]]) that gives you access to property strings through the DOM. | [[http://open-ils.org/cgi-bin/viewcvs.cgi/ILS/Evergreen/staff_client/chrome/locale/en-US/evergreen/|CVS]] |