chrome registry needs to allow dir and jar destinations

RESOLVED INVALID

Status

SeaMonkey
General
P3
normal
RESOLVED INVALID
18 years ago
13 years ago

People

(Reporter: Warren Harris, Assigned: David Hyatt)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: nsbeta2)

(Reporter)

Description

18 years ago
We need a way to allow some chrome files to come out of directories while others 
come out of jar files -- for the same chrome package. The navigator package is 
the major culprit here, since its files are scattered throughout the tree, and 
we'd like to be able to convert one directory at a time to package its chrome 
stuff into a jar file.

Today, we discussed a way to do this, where when the chrome registry parses the 
installed-chrome.txt file, it will (temporarily) add a parallel entry to check 
in a corresponding jar file. E.g. if the installed-chrome.txt file says this:

  skin,install,url,resource:/chrome/skins/modern

it behind the scenes registers 'resource:/chrome/skins/modern' and 
'jar:resource:/chrome/skins/modern.jar!/' as resource substitutions for 
"Chrome,skin,navigator" such that:

  resource://Chrome,skin,navigator/foo.css

tries first to resolve to:

  resource:/chrome/skins/modern/foo.css

and then tries:

  jar:resource:/chrome/skins/modern.jar!/foo.css

(or does that have to be in the other order?)

Hmmm... I'm forgetting the rest...
(Reporter)

Comment 1

18 years ago
FYI, I also added nsIResProtocolHandler::HasSubstitutions for this.
(Assignee)

Comment 2

18 years ago
Sweet.  I'll get this whipped up by tomorrow sometime.  
(Reporter)

Comment 3

18 years ago
Yo. What's up with this? We're ready!
(Assignee)

Comment 4

18 years ago
Went on vacation for a week.  Back now.  Anyway, seeing as how some pointy-head 
will chew me out if I work on this bug and/or check code in without the bug 
first being nsbeta2+, I'm nominating it for nsbeta2.
Status: NEW → ASSIGNED
Keywords: nsbeta2
Whiteboard: nsbeta2

Comment 5

18 years ago
hyatt says dprice and warren don't need this after all.  resolving as invalid.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
(Reporter)

Comment 6

18 years ago
Well, we don't _need_ it, but developers would probably want to have it. Oh 
well.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.