Development/Firefox Extensions/Chrome 1 Chrome Package The files for a package are usually combined into a single JAR file. Packages may also be accessed in expanded form into a directory. (handy during development since you can edit the file directly and then reload the XUL file without having to repackage or reinstall the files). There are usually three different parts to a chrome package, although they are all optional. Each part is stored in a different directory. These three sets are: * Content - Windows and scripts * Skin - Style sheets, images and other theme specific files * Locale - Locale specific files {image:http://wiki.marandcustomsolutions.com/space/Development/Firefox+Extensions/Chrome/Firefox_ext_content_package_overview.jpg} 1.1 Content - Windows and scripts The declarations of the windows and the user interface elements contained within them. These are stored in XUL files, which have a xul extension. A content package can have multiple XUL files, but the main window should have a filename that is the same as the package name. For example, the editor package will have a file within it called editor.xul. Scripts are placed in separate files alongside the XUL files. 1.1 Skin - Style sheets, images and other theme specific files Style sheets describe details of the appearance of a window. They are stored separately from XUL files to facilitate modifying the skin (theme) of an application. Any images used are stored here also. 1.1 Locale - Locale specific files All the text that is displayed within a window is stored separately. This way, a user can have a set for their own language. 2006-03-15 16:39:01.0 2006-03-15 11:27:55.0 Firefox_ext_content_package_overview.jpg Wed Mar 15 16:38:16 EST 2006