[Techtalk] Mozilla/Firefox customization

[Riccarda Cassini]

Dominik Schramm wrote:
> "Riccarda Cassini" <riccarda.cassini at gmx.de> writes:
> > Funnily, there actually appears to be an "about:about". At least
> > that's what the existence of the code line
> >
> >     { "about", "chrome://global/content/aboutAbout.html", PR_FALSE }
> >
> > suggests to me. Typing "about:about" has no effect, though... 
> 
> I'm using Mozilla 1.6, and this does have an effect:
> it shows a list of all "about:" possibilites: [...]

Thanks Dominik!  So now, I'm happy with the final, official list, at
least for Mozilla :-)  I guess my problem is that I was looking at the
source of Mozilla to find out things about Firefox - which is about
equally useful as looking at the code of "tar" when trying to learn
something about "jar" ;-)  Despite the similarities, there seem to be
differences between Firefox and Mozilla... [*]


> > I tried hunting for that "aboutAbout.html", but it doesn't seem to
> > be included anywhere with the files that come with the Firefox
> > installation. Not even hidden somewhere in one of the .jar files.
> > Well, maybe it's planned for future versions to come...
> 
> I found it here:
> /usr/local/mozilla/chrome/toolkit.jar

I tried (from my Firefox installation directory):

$ find . -name "*.jar" -exec jar tf {} \; | grep -i about | sort
content/browser/about.png
content/browser/aboutCredits.png
content/browser/aboutDialog.css
content/browser/aboutDialog.js
content/browser/aboutDialog.xul
content/browser/aboutFooter.png
content/mozapps/extensions/about.js
content/mozapps/extensions/about.xul
locale/en-US/browser/aboutDialog.dtd
locale/en-US/global/about.xhtml
locale/en-US/mozapps/extensions/about.dtd
skin/classic/mozapps/extensions/about.css

...which led me to make the above assertion.

> 
> > (My guess about that "chrome://" protocol is, that it is typically
> > referring to internal files - I could be wrong, though...)
> 
> chrome:// URIs refer to stuff under the chrome subdirectories in the
> mozilla installation directory and the user's profile directory.  

thanks for confirming this.

Riccarda


[*] In this context, I've always wondered how they manage to
reincorporate any progress made in one code base into the other
(Mozilla <-> Firefox), if so desired.  I.e., how are the common parts
kept in sync?  As I understand, Phoenix originally branched off from
the Mozilla code. Quite some time has passed by since, and both
browsers have matured considerably. Manually merging any useful
addition every time looks like a laborious task to me...
Are there any tools that ease or partially automatize this process?
(I mean tools for the merging step, not for plain revision control.)
Any of you gurus happen to know, accidentally?




-- 
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info