If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[feature] make chrome registry point into jar by default

RESOLVED FIXED in M16

Status

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

People

(Reporter: Warren Harris, Assigned: David Hyatt)

Tracking

({verifyme})

Trunk
All
Other
verifyme
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: 1/2 day, depends 18433)

(Reporter)

Description

18 years ago
We need to rework the chrome registry and chrome urls to map to jar files. 

The latest word on this was the thread: 
news://news.mozilla.org/3838BA4B.4963840C%40netscape.com
(Reporter)

Updated

18 years ago
Blocks: 18433
Depends on: 18432
(Reporter)

Updated

18 years ago
Target Milestone: M14
(Assignee)

Comment 1

18 years ago
I am of the opinion (still, after more thought) that the search path should be 
hardcoded in 5.0, since to do it any other way requires making the UI cumbersome 
(since the search path must necessarily be exposed to the user because two 
JARs might share the same skin).
(Reporter)

Updated

18 years ago
Keywords: beta1
Reports from M13 usage is that it can take as much as 200MB (!!) to install 
Seamonkey on the mac (non hfs+ disks, which are still very common). Please let us 
fix this for beta or we are really going to be the laughing stock of the solar 
system.

Comment 3

18 years ago
[PDT+]
Whiteboard: [PDT+]

Comment 4

18 years ago
Do we really know how much work this will be?  In my last conversation with 
Hyatt on this, it seemed like it would take scrubbing through large sections of 
the code to get the true benefits of this.  The bug is titled "rework chrome 
URLs..." but isn't it the case that once we have the ability to reference chrome 
URLs in JAR files, we will need to reorgainize all of the XUL files so that they 
can live in JARs?

It was following this line of reasoning that led David and myself to concluded 
that this couldn't be done for Beta (this is a good chunk of the work that needs 
to be done to make the app truly skinnable as well).
(Assignee)

Comment 5

18 years ago
I am of the opinion that this could probably wait until after beta1.  Doing the 
conversion is going to take time and involve hacking the chrome registry.  It 
will affect i18n and the localization folks, who are expecting to have locale 
switching working by beta1 (and now have it working using the current scheme).

If we do switch over to jars, we'll end up having to go the whole nine yards, 
since I don't think we can break locale switching in beta1.
(Reporter)

Comment 6

18 years ago
Chris S. says he wouldn't hold beta for this now.

Erasing PDT+ designation.
Whiteboard: [PDT+]

Updated

18 years ago
Whiteboard: [PDT-]
(Reporter)

Comment 7

18 years ago
Moving to M15.
Target Milestone: M14 → M15
(Reporter)

Comment 8

18 years ago
Marking beta2.
Keywords: beta2
(Reporter)

Comment 9

18 years ago
Hyatt should own this part now. 
Assignee: warren → hyatt

Comment 10

18 years ago
Adding 'skins' keyword to selected chrome bugs.  Please add any omissions.  
Sorry for any mistakes...
Keywords: skins
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
Keywords: beta1
Whiteboard: [PDT-]
Target Milestone: M15 → M16

Updated

18 years ago
Blocks: 29160

Comment 11

18 years ago
Mass-moving all M16 non-feature bugs to M17, which we still consider to be 
part of beta2
Target Milestone: M16 → M17
(Reporter)

Comment 12

18 years ago
Since when is this not a feature bug? I think we this needs to be done sooner 
rather than later so that we have time to work the kinks out.
Target Milestone: M17 → M16

Comment 13

18 years ago
You're right, this should have been marked as feature, doing so now. Thanks for 
moving it back.
Summary: rework chrome urls to map to jar files → [feature] rework chrome urls to map to jar files

Comment 14

18 years ago
Mass-adding beta2 keyword to all skins bugs.
(Assignee)

Comment 15

18 years ago
This bug is dependent on getting the chrome resources actually bundled into 
JARs.
Summary: [feature] rework chrome urls to map to jar files → [feature] make chrome registry point into jar by default
Whiteboard: 1/2 day
(Assignee)

Updated

18 years ago
Whiteboard: 1/2 day → 1/2 day, 4/28

Updated

18 years ago
Keywords: nsbeta2

Comment 16

18 years ago
What jar work is this depending on?
Whiteboard: 1/2 day, 4/28 → 1/2 day, ??/?? DEPENDENCY?

Comment 17

18 years ago
[nsbeta2-] since Phil thinks JARs out for beta2
Whiteboard: 1/2 day, ??/?? DEPENDENCY? → [nsbeta2-] 1/2 day, ??/?? DEPENDENCY?
(Reporter)

Comment 18

18 years ago
No, this has to go in. I think Hyatt's done it already anyway.
Whiteboard: [nsbeta2-] 1/2 day, ??/?? DEPENDENCY? → 1/2 day, ??/?? DEPENDENCY?

Comment 19

18 years ago
No, he says it is 5 minutes for him, but cannot be done until after some JAR 
work we don't have the bug # for.  Does anyone know?

Comment 20

18 years ago
18433 is the repackaging bug this depends on, not the other way around.
Removing 18433 from the blocks list, will add to depends next.

No longer blocks: 18433
Whiteboard: 1/2 day, ??/?? DEPENDENCY? → 1/2 day, depends 18433

Comment 21

18 years ago
18433 is the repackaging bug that results in jars for this bug.  Adding to
dependency list and updating status whiteboard.
Depends on: 18433
(Assignee)

Comment 22

18 years ago
the chrome registry is now ready and willing to point into jars.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 23

18 years ago
*spam* changing qa contact from nobody@mozilla.org to me (BlakeR1234@aol.com) 
on 121 open or resolved (but not verified) bugs.  sorry for the spam everybody, 
but most of these bugs would just remain dormant and not checked by QA 
otherwise.  I'm not sure how so many bugs have nobody as their QA contact, but 
I suspect this is the fault of some sort of bugzilla corruption that happened 
at some point (most of these bugs are in the 20000-26000 range, and I don't see 
where in the activity log that QA contact explicitly changed to 
nobody@mozilla.org)

Anyways, sorry again for spam.  If you really get annoyed, I'm usually 
available in #mozilla on IRC for torture.
QA Contact: nobody → BlakeR1234

Updated

17 years ago
Keywords: verifyme
QA Contact: blakeross → doronr

Updated

17 years ago
Keywords: skins
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.