Back to index

lightning-sunbird  0.9+nobinonly
Public Member Functions | Public Attributes
nsIToolkitChromeRegistry Interface Reference

import "nsIToolkitChromeRegistry.idl";

Inheritance diagram for nsIToolkitChromeRegistry:
Inheritance graph
[legend]
Collaboration diagram for nsIToolkitChromeRegistry:
Collaboration graph
[legend]

List of all members.

Public Member Functions

void processContentsManifest (in nsIURI aOldManifestURI, in nsIURI aFile, in nsIURI aBaseURI, in boolean aAppend, in boolean aSkinOnly)
 The "canonical" manifest is a plaintext file which sits outside of a JAR file.
void checkForOSAccessibility ()
 If the OS has a "high-visibility" or "disabled-friendly" theme set, we want to force mozilla into the classic theme, which (for the most part obeys the system color/font settings.
nsIUTF8StringEnumerator getLocalesForPackage (in AUTF8String aPackage)
 Get a list of locales available for the specified package.
void reloadChrome ()
ACString getSelectedLocale (in ACString packageName)
void refreshSkins ()
boolean allowScriptsForPackage (in nsIURI url)
 Installable skin XBL is not always granted the same privileges as other chrome.
nsIURI convertChromeURL (in nsIURI aChromeURL)
 Resolve a chrome URL to an loadable URI using the information in the registry.
void checkForNewChrome ()
 refresh the chrome list at runtime, looking for new packages/etc

Public Attributes

const PRInt32 NONE = 0
const PRInt32 PARTIAL = 1
const PRInt32 FULL = 2

Detailed Description

Definition at line 45 of file nsIToolkitChromeRegistry.idl.


Member Function Documentation

Installable skin XBL is not always granted the same privileges as other chrome.

This asks the chrome registry whether scripts are allowed to be run for a particular chrome URI. Do not pass non-chrome URIs to this method.

refresh the chrome list at runtime, looking for new packages/etc

If the OS has a "high-visibility" or "disabled-friendly" theme set, we want to force mozilla into the classic theme, which (for the most part obeys the system color/font settings.

We cannot do this at initialization, because it depends on the toolkit (GTK2) being initialized, which is not the case in some embedding situations. Embedders have to manually call this method during the startup process.

nsIURI nsIChromeRegistry::convertChromeURL ( in nsIURI  aChromeURL) [inherited]

Resolve a chrome URL to an loadable URI using the information in the registry.

Does not modify aChromeURL.

Chrome URLs are allowed to be specified in "shorthand", leaving the "file" portion off. In that case, the URL is expanded to:

chrome://package/provider/package.ext

where "ext" is:

"xul" for a "content" package, "css" for a "skin" package, and "dtd" for a "locale" package.

Parameters:
aChromeURLthe URL that is to be converted.

Get a list of locales available for the specified package.

ACString nsIXULChromeRegistry::getSelectedLocale ( in ACString  packageName) [inherited]
void nsIToolkitChromeRegistry::processContentsManifest ( in nsIURI  aOldManifestURI,
in nsIURI  aFile,
in nsIURI  aBaseURI,
in boolean  aAppend,
in boolean  aSkinOnly 
)

The "canonical" manifest is a plaintext file which sits outside of a JAR file.

To provide backwards-compatibility with contents.rdf, we provide this function which reads a contents.rdf manifest and writes it to a file.

Parameters:
aOldManifestURIThe URI of an old manifest to read, without the trailing "contents.rdf", e.g. "jar:resource:///chrome/foo.jar!/content/foo/" or "file://path/to/contents/rdf/"
aFileThe URI of a manifest file to write. It's a good idea to use a resource: URI if possible.
aBaseURIThe base URI for relative path creation "jar:resource:///chrome/foo.jar!/content/foo/" this is a separate param from aOldManifestURI so the "contents.rdf" can be read outside of the jar to keep the zipreader cache from holding it open.
aAppendWhether we should append to an existing manifest or truncate and start empty.
aSkinOnlyOnly allow skin packages.

Member Data Documentation

Definition at line 51 of file nsIChromeRegistry.idl.

Definition at line 49 of file nsIChromeRegistry.idl.

Definition at line 50 of file nsIChromeRegistry.idl.


The documentation for this interface was generated from the following file: