5
edits
Gecko:Chrome Registration: Difference between revisions
Jump to navigation
Jump to search
m
→The Current Registration Process
Kris0shannon (talk | contribs) |
|||
| Line 5: | Line 5: | ||
The first part of the chrome registration process identifies a list of locations to register. For chrome installed as part of the application, this is handled by a manifest file called "installed-chrome.txt". This file lists locations of chrome packages. In toolkit applications, this is also handled by the extension manager. The EM keeps a list of enabled extensions, and provides a list of chrome package locations to the chrome registry. | The first part of the chrome registration process identifies a list of locations to register. For chrome installed as part of the application, this is handled by a manifest file called "installed-chrome.txt". This file lists locations of chrome packages. In toolkit applications, this is also handled by the extension manager. The EM keeps a list of enabled extensions, and provides a list of chrome package locations to the chrome registry. | ||
The manifest/registrations are not read at every startup. Instead, the chrome registry keeps a cache of the package information. It updates this cache when the modification-time of installed-chrome.txt changes, or when the EM determines that the set of installed extensions has changed. | The manifest/registrations are not read at every startup. Instead, the chrome registry keeps a cache of the package information (extensions.cache). It updates this cache when the modification-time of installed-chrome.txt changes, or when the EM determines that the set of installed extensions has changed. | ||
The second part of chrome registration looks at each chrome package for an RDF file (contents.rdf) describing the package. This RDF file describes the package name and any overlays or style-overlays that the package provides. In seamonkey, this RDF file also defines version numbers for content, locale, and skin packages, so that only properly-versioned locale and skin packages are applied to a content package. In toolkit applications, this is not necessary, because the EM handles all version-checking before the chrome registry sees any chrome packages. | The second part of chrome registration looks at each chrome package for an RDF file (contents.rdf) describing the package. This RDF file describes the package name and any overlays or style-overlays that the package provides. In seamonkey, this RDF file also defines version numbers for content, locale, and skin packages, so that only properly-versioned locale and skin packages are applied to a content package. In toolkit applications, this is not necessary, because the EM handles all version-checking before the chrome registry sees any chrome packages. | ||