Closed Bug 72717 Opened 24 years ago Closed 24 years ago

die Blue, die!

Categories

(SeaMonkey :: Themes, defect, P3)

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9

People

(Reporter: hewitt, Assigned: hewitt)

Details

Attachments

(2 files)

The Blue theme must die. For the interests of 0.8.1, Asa has asked me to simply land something on the 0.8.1 branch to prevent blue from being built. So I will do that first and ask for reviews. Then, later on I'll actually cvs remove it from the trunk.
Attached patch patch to prevent building blue (deleted) — Splinter Review
r=blake
a=asa. Thanks Joe.
When it's done, I suppose bugs such as 66078 or 72033 can be resolved as WONTFIX ?
fixed on branch. Yes, from here on all Blue bugs should be marked WONTFIX.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
hewitt, we talked about a light-weight replacement for Blue. Is there anything you or Netscape can help with? The same goes for anyone else who feels this would be a nice challenge: It doesn't need to be a shiny skin, just functional, quick, and (or is this just wishful thinking?) low on memory use. My idea behind this is that it can also be used as a (simple!) example of how to skin chrome and I'm hoping it's pretty low maintainance (and thus more robust than the more involved skins). I should probably open a new RFE/bug for this :-)
You guys just have no mercy. Blue was the only aesthetically pleasing skin, friendly on resources, unintrusive, with the dignity of the plainness, 3D-free, form follows function, etc., etc. Goodbye, my beloved skin! Peter, I second your RFE if you post it and will vote for it if you let us know which bug-ID it gets. Thanks!
Note that you can still pull by date from CVS and get the blue files (or just grab and hold onto a build pre-removal) Anyone interested is free to take and maintain blue as a XPInstallable theme. I also like the idea of a simple theme with code that is as discoverable (for new folks learning skinning) as possible.
Keywords: nsbeta1
Themes Triage Team Marking nsbeta1+
Keywords: nsbeta1nsbeta1+
Priority: -- → P3
The forthcoming patch removes all references to the blue theme from various build and install packaging files. Of course, in addition to the patch I will be doing a cvs remove of mozilla/themes/blue.
Attached patch patch to kill blue (deleted) — Splinter Review
I don't get the nsbeta1+ for something that wasn't in the NS build anyway; adding nearest mozilla equiv for tracking though I suppose that's a moot point as this is about to be checked in. r=dveditz You missed a commented-out ";bin\chrome\blue\*" line in mozilla/xpinstall/packager/packages-win. It won't hurt anything to leave it, but it'd be nice if you could zap that one too.
Keywords: mozilla0.9
sr=hyatt. You may fire at will.
Blue is dead, long live Blue.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Oh, by the way, if you ever get the urge to check out blue, I tagged it in the tree as BLUETHEME_LASTGASP_20010410
It was forgotten to remove it from the 'View' & 'Themes' menus.
rbs: I think those are dynamically generated during build time. AFAIK you've got to change some RDF in your profile to remove these in already existing profiles.
Marking verified.
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: