W3C home > Mailing lists > Public > www-style@w3.org > April 1997

RE: The concept of cascading

From: Chris Wilson (PSD) <cwilso@MICROSOFT.com>
Date: Mon, 28 Apr 1997 19:22:58 -0700
Message-ID: <41F7F4CE3CA2CF11BC5000805F14B2A90174B579@RED-31-MSG.dns.microsoft.com>
To: "'Paul Prescod'" <papresco@calum.csclub.uwaterloo.ca>, David Perrell <davidp@earthlink.net>
Cc: www-style@w3.org
I'd say you just answered your own question.

	-Chris
Chris Wilson
cwilso@microsoft.com
***

> -----Original Message-----
> From:	Paul Prescod [SMTP:papresco@calum.csclub.uwaterloo.ca]
> Sent:	Monday, April 28, 1997 7:05 PM
> To:	David Perrell
> Cc:	www-style@w3.org
> Subject:	Re: The concept of cascading
> 
> David Perrell wrote:
> > Perhaps I'm all wet, but I don't see site maintenance being
> > torrentially anarchized by cascading stylesheets. I was referring to
> > documents styled for the department from which they're generated,
> not
> > on-the-fly-customized for the requestor. Control over appearance is
> > gained with a few centrally-controlled stylesheets, not lost. As for
> > specifying stylesheets and elements based on parameters, that's
> getting
> > pretty trivial using server-side scripting such as ASP. Though not
> > necessary with SS-scripting, using external cascading stylesheets
> could
> > still simplify maintenance.
> 
> I don't understand the benefit of cascading over parameterization.
> With
> parameterization the person in the central design office says exactly
> what can be changed and the departments supply "stubs" that do the
> changing. With the cascade, they can change whatever they feel like.
> 
>  Paul Prescod
Received on Monday, 28 April 1997 22:23:02 GMT

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