Re: Parsing .css files with php: Cons? [message #176767 is a reply to message #176763] |
Sun, 22 January 2012 23:14 |
Peter H. Coffin
Messages: 245 Registered: September 2010
Karma:
|
Senior Member |
|
|
On Sun, 22 Jan 2012 22:35:08 +0100, Michael Fesser wrote:
> A typical short-sighted answer.
>
> Another example: Assuming I want to use different color schemes on
> different parts of the website, each with different nuances of the
> base color. Of course I could edit the CSS by hand and calculate all
> needed values by myself - a background color here, a border color
> there, some text colors and others -, but I could also let PHP do
> the work: I just define the base color and all others are calculated
> automatically.
>
> And there are many other situations where some programming or
> conditional logic in the CSS might come in handy, which has absolutely
> nothing to do with your "properly created" CSS.
>
> The only question - and what this sub-thread is all about - is whether
> you want to have the CSS script parsed everytime or if you want
> to cache the result. The latter is what Chuck does by calling his
> generator script.
No.
You supply secondary ones that override the master/main one. Master one
referred to by absolute location, site-section overrides use relative
location*, per-page overrides get embedded. That's why they're called
"Cascading".
----------------------
* You are sectioning your site by directory hierarchy, aren't you? If
not, you richly deserve whatever you get. If you're depending on a
CMS, let the CMS deal with it.
--
Frankly, your argument wouldn't float were the sea composed of mercury.
-- Biff
|
|
|