Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #4578
| Path | csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail |
|---|---|
| From | "Peter H. Coffin" <hellsop@ninehells.com> |
| Newsgroups | comp.lang.php |
| Subject | Re: Parsing .css files with php: Cons? |
| Date | Sun, 22 Jan 2012 17:14:59 -0600 |
| Organization | A noiseless patient Spider |
| Lines | 36 |
| Message-ID | <slrnjhp63j.51n.hellsop@nibelheim.ninehells.com> (permalink) |
| References | <e51383e9-cfa4-4f68-b5a1-36b024d4cd85@o9g2000yqa.googlegroups.com> <83gih757lb1shbfamuk67juagcmftmiu0d@mfesser.de> <65ce085f-7e7d-4ae3-af69-f96370944eac@m11g2000yqe.googlegroups.com> <u0tih7dujcepc0r4td8jf4trspbvbdtnna@mfesser.de> <jfd5l1$cmc$1@dont-email.me> <9nv6n4F6anU1@mid.individual.net> <jff3rm$das$1@dont-email.me> <jff8ks$8jc$1@dont-email.me> <agamh75s155va4u0c6p860sfcbpqvi6gsc@mfesser.de> <jffd0o$2qo$1@dont-email.me> <hbuoh7hlvc44c9n8h55j0qlfmk3ik68e08@mfesser.de> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=us-ascii |
| Content-Transfer-Encoding | 7bit |
| Injection-Info | mx04.eternal-september.org; posting-host="le/2G4+BNpieVhQI6uJ2Lw"; logging-data="31833"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18z0AuSmR7sZV0iXxi8kpEW" |
| User-Agent | slrn/0.9.9p1 (OpenBSD) |
| Cancel-Lock | sha1:E5zqIDDv3g5IiQ3V4mZUOqtn8P8= |
| Xref | x330-a1.tempe.blueboxinc.net comp.lang.php:4578 |
Show key headers only | View raw
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
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Parsing .css files with php: Cons? "J. Frank Parnell" <juglesh@gmail.com> - 2012-01-16 13:36 -0800
Re: Parsing .css files with php: Cons? Erwin Moller <erwinmollerusenet@xs4all.nl> - 2012-01-17 11:42 +0100
Re: Parsing .css files with php: Cons? "Álvaro G. Vicario" <alvaro.NOSPAMTHANX@demogracia.com.invalid> - 2012-01-17 13:31 +0100
Re: Parsing .css files with php: Cons? Captain Paralytic <paul_lautman@yahoo.com> - 2012-01-17 04:32 -0800
Re: Parsing .css files with php: Cons? "J. Frank Parnell" <juglesh@gmail.com> - 2012-01-19 12:45 -0800
Re: Parsing .css files with php: Cons? Captain Paralytic <paul_lautman@yahoo.com> - 2012-01-20 02:07 -0800
Re: Parsing .css files with php: Cons? Michael Fesser <netizen@gmx.de> - 2012-01-20 11:25 +0100
Re: Parsing .css files with php: Cons? Captain Paralytic <paul_lautman@yahoo.com> - 2012-01-20 05:33 -0800
Re: Parsing .css files with php: Cons? Michael Fesser <netizen@gmx.de> - 2012-01-20 15:05 +0100
Re: Parsing .css files with php: Cons? Chuck Anderson <cycletourist@invalid.invalid> - 2012-01-20 18:50 -0700
Re: Parsing .css files with php: Cons? "J.O. Aho" <user@example.net> - 2012-01-21 08:10 +0100
Re: Parsing .css files with php: Cons? Chuck Anderson <cycletourist@invalid.invalid> - 2012-01-21 12:31 -0700
Re: Parsing .css files with php: Cons? Jerry Stuckle <jstucklex@attglobal.net> - 2012-01-21 15:53 -0500
Re: Parsing .css files with php: Cons? Michael Fesser <netizen@gmx.de> - 2012-01-21 22:22 +0100
Re: Parsing .css files with php: Cons? "Beauregard T. Shagnasty" <a.nony.mous@example.invalid> - 2012-01-21 21:37 +0000
Re: Parsing .css files with php: Cons? Michael Fesser <netizen@gmx.de> - 2012-01-22 22:35 +0100
Re: Parsing .css files with php: Cons? Jerry Stuckle <jstucklex@attglobal.net> - 2012-01-22 19:19 -0500
Re: Parsing .css files with php: Cons? Jerry Stuckle <jstucklex@attglobal.net> - 2012-01-21 17:08 -0500
Re: Parsing .css files with php: Cons? Chuck Anderson <cycletourist@invalid.invalid> - 2012-01-21 18:17 -0700
Re: Parsing .css files with php: Cons? Jerry Stuckle <jstucklex@attglobal.net> - 2012-01-21 23:14 -0500
Re: Parsing .css files with php: Cons? Michael Fesser <netizen@gmx.de> - 2012-01-22 22:35 +0100
Re: Parsing .css files with php: Cons? "Peter H. Coffin" <hellsop@ninehells.com> - 2012-01-22 17:14 -0600
Re: Parsing .css files with php: Cons? Jerry Stuckle <jstucklex@attglobal.net> - 2012-01-22 19:21 -0500
Re: Parsing .css files with php: Cons? Michael Fesser <netizen@gmx.de> - 2012-01-23 23:44 +0100
csiph-web