8.1. Hacks 84-9084. Do Groundwork for Extension Development8.2.1. Spot Extension Files8.2.2. Spot Extension Installers8.2.3. Three Kinds of RDF Files8.2.4. Compare Locales, Themes, Applications, and Extensions8.2.5. Find the XPInstall Missing Link85. Study Packages with the Chrome Manager8.3.1. Get the Chrome Manager8.3.2. Chrome Simplified8.3.3. Understand Packages8.3.4. Packages Versus Extensions86. Create a Chrome Package8.4.1. Create a Local Folder Hierarchy8.4.2. Create a Package Representation8.4.2.1. Flat file structure8.4.2.2. JAR representation8.4.2.3. Default URL names for package files8.4.3. Register a Package with the Chrome Registry8.4.3.1. Make a contents.rdf manifest file8.4.3.2. Use the new chrome: URLs87. Make a Bottom-Up Overlay8.5.1. Adding an Item8.5.1.1. Register the overlay8.5.1.2. The overlay file8.5.2. Other Places to Overlay8.5.3. Adding a Sidebar8.5.4. Under the Covers8.5.5. Skin Overlays88. Make, Bundle, and Publish an XPI8.6.1. Making a Firefox XPI File8.6.2. Understanding install.rdf8.6.3. The First Big Release8.6.3.1. Using Mozilla Update8.6.3.2. DIY publishing8.6.4. Distribute Software Updates89. Build an Installable Theme8.7.1. Getting the Content Together8.7.1.1. Do the creative bit8.7.1.2. Do the systematic bit8.7.1.3. Collect together skins8.7.2. Building the Theme JAR File8.7.2.1. Build an install-bundled theme8.7.2.2. Build skins into downloadable extensions8.7.2.3. Build skins into complete and separately downloadable
themes8.7.3. Installation Support90. Identify Reusable Toolkits8.8.1. Poking Around Inside toolkit.jar8.8.1.1. The global package8.8.1.2. The xul.css master XBL stylesheet8.8.1.3. The mozapps package8.8.2. Scavenging Application Pieces8.8.3. Finding Embedded Components8.8.4. Reusing Script Libraries