W3C home > Mailing lists > Public > www-style@w3.org > December 1998

RE: New W3C Note about suggested CSS extensions

From: Jelks Cabaniss <jelks@jelks.nu>
Date: Mon, 28 Dec 1998 21:41:31 -0500
To: "Chris Lilley" <chris@w3.org>
Cc: <www-style@w3.org>, <bert@w3.org>
Message-ID: <NBBBICMNIPCICMKJECCBIENLCHAA.jelks@jelks.nu>
> > > Some people find it more convenient to use grouping for other
> > > purposes, and use a symbolic constant instead. E.g.:

> > Why would using @define preclude grouping?  Why couldn't you say:
> >
> >         @define orange = #faa;         ...
> >         H1, H2, H3 {color: orange};

> It doesn't preclude that; it just doesn't require it.
>
> The idea is to only need a single editing change if you want to adjust
> that color in a stylesheet, and be sure of hitting all occurences. Also,
> to isolate possibly different uses of the same color (which would likely
> be bad design anyway, but could happen).
>
> Its a maintainability convenience.

Aha, thanks!  This is virtually identical to (and has the same purpose of) the
"named styles" suggestion, but is slightly more restrictive.  Could the above
concept be expanded to handle something like:

	@define myTheme = "color: navy; background: #eee; border: 3px #ccc outset";
	...
	h3 { myTheme; font-size: 1.1em }
	p.standout { myTheme; font-size: .8em }


/Jelks
Received on Monday, 28 December 1998 21:41:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:53:56 GMT