Bugzilla CSS plan

[Christian Robottom Reis]

On Tue, Jul 27, 2004 at 11:36:17AM -0700, Maxwell Kanat-Alexander wrote:
> On Fri, 2004-07-23 at 19:36, Christian Robottom Reis wrote:
> > > 	Oh, a fine idea. What would be against having a custom stylesheet for
> > > the page-specific ones, as well? They'll be empty files, the worst that
> > > will happen is extra hits on Apache.
> > 
> > I claim YAGNI -- overriding page-specific CSS can be done in custom.css
> > and that's enough for most purposes; full-blown skins can replace more
> > files if they like, but won't have the cvs-update-protection that
> > custom.css gets.
> 
> 	Huh... I'm very wary of saying YAGNI when it comes to extensibility
> 	of Bugzilla. From what I've seen, everybody's favorite thing to do
> 	is customize Bugzilla as soon as they get their hands on it.

Maybe. Maybe skins are mainly coming up as an alternative to the sorry
state of our user interface.

(I honestly don't see what skins would give us that wouldn't need to be
complemented by custom fields and template changes, unless it's fixing
our user interface without going through the Bugzilla patch approval
process!)

At any rate, the fact that other people have replied decrying my
simple-minded proposal gives me more incentive to fix the interface
soon, before we actually get skins -- who knows, maybe I can *make* them
YAGNI <wink>.

> 	Anyhow, what I'd really want do as a Bugzilla admin is modify the
> shipped CSS files, and then add a bit of custom CSS. I wouldn't just
> modify the custom.css. 

Note that custom.css would apply *last* of all styles applied; this
means you wouldn't *need* to modify anything but custom.css -- rules
defined there would override other rules previously defined.

Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331