Changes

Jump to: navigation, search

Chrome

2,915 bytes added, 09:40, 6 October 2006
Chrome Registry
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).
 
 
==Code Registry Example==
<pre>
1. content necko jar:comm.jar!/content/necko/ xpcnativewrappers=yes
2. locale necko en-US jar:en-US.jar!/locale/en-US/necko/
3. content xbl-marquee jar:comm.jar!/content/xbl-marquee/
4. content pipnss jar:pipnss.jar!/content/pipnss/
5. locale pipnss en-US jar:en-US.jar!/locale/en-US/pipnss/
6. # Firefox-only
7. overlay chrome://browser/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}
8. overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul
9. overlay chrome://navigator/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org
10. content pippki jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes
11. locale pippki en-US jar:en-US.jar!/locale/en-US/pippki/
12. content global-platform jar:toolkit.jar!/content/global-platform/ platform
13. skin global classic/1.0 jar:classic.jar!/skin/classic/global/
14. override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml
15. content inspector jar:inspector.jar!/content/inspector/ xpcnativewrappers=no
</pre>
 
*Line 1: <pre>content packagename uri/to/files/ [flags]</pre>
**This code will register the package called necko when resolving the URL jar:comm.jar!/content/necko/ with the xpcnativewrappers flag on
 
 
*Line 5: <pre>locale packagename localename uri/to/files/ [flags]</pre>
**This code will register a locale package called pinpnss with the localename en-US when resolving the URL jar:en-US.jar!/locale/en-US/pipnss/
**NOTE: If there are more than one locale file register for the package, chrome will select the best-fit locale for the URL.
 
 
*Line 6: <pre># this line is a comment - you can put whatever you want here</pre>
**To comment your code, put '#' in the beginning of the line.
 
 
*Line 7: <pre>overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]</pre>
**The prupose of this code is to overlaying one chrome on top of the other. The application={ec8030f7-c20a-464f-9b0e-13a3a9e97384} is a flag that specific which application will have this overlay.
 
 
*Line 13: <pre>skin packagename skinname uri/to/files/ [flags]</pre>
**This will register a skin package gobal with the skinname classic/1.0 when resolving the URL jar:classic.jar!/skin/classic/global/
**NOTE: If more than one skin register for the package, chrome will select the best-fit skin for the URL.
 
 
*Line 14: <pre>override chrome://package/type/original-uri.whatever new-resolved-URI [flags]</pre>
**The purpose of this is to override a chrome file provided by the application or XULRunner with a new extension or embedder.
=Additional Info=
1
edit

Navigation menu