Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #4486 > unrolled thread
| Started by | "J. Frank Parnell" <juglesh@gmail.com> |
|---|---|
| First post | 2012-01-16 13:36 -0800 |
| Last post | 2012-01-23 23:44 +0100 |
| Articles | 4 on this page of 24 — 10 participants |
Back to article view | Back to comp.lang.php
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
Page 2 of 2 — ← Prev page 1 [2]
| From | Michael Fesser <netizen@gmx.de> |
|---|---|
| Date | 2012-01-22 22:35 +0100 |
| Message-ID | <hbuoh7hlvc44c9n8h55j0qlfmk3ik68e08@mfesser.de> |
| In reply to | #4560 |
.oO(Jerry Stuckle) >On 1/21/2012 4:22 PM, Michael Fesser wrote: >> >> The whole point of using PHP for creating the CSS is to avoid having to >> edit a dozen places in the CSS to change some color for example. Instead >> you make use of PHP and variables. Much simpler. >> >> And if you still want a "static" CSS for performance reasons, you have >> to preprocess it. Calling a script for doing this is not much work. >> Dependent on the used IDE this could even be automated in the build and >> upload process. > >Create your .css properly and you don't need to do that. 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. Micha -- http://mfesser.de/blickwinkel
[toc] | [prev] | [next] | [standalone]
| From | "Peter H. Coffin" <hellsop@ninehells.com> |
|---|---|
| Date | 2012-01-22 17:14 -0600 |
| Message-ID | <slrnjhp63j.51n.hellsop@nibelheim.ninehells.com> |
| In reply to | #4574 |
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
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2012-01-22 19:21 -0500 |
| Message-ID | <jfi95i$irg$2@dont-email.me> |
| In reply to | #4578 |
On 1/22/2012 6:14 PM, Peter H. Coffin wrote: > 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". > Exactly! -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Michael Fesser <netizen@gmx.de> |
|---|---|
| Date | 2012-01-23 23:44 +0100 |
| Message-ID | <rcorh7ljohdlu6rfl70bgt7cgs242ua6qq@mfesser.de> |
| In reply to | #4578 |
.oO(Peter H. Coffin) >On Sun, 22 Jan 2012 22:35:08 +0100, Michael Fesser wrote: >> >> 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". What does this have to do with the issue discussed in this thread? Of course I make use of the cascade where appropriate. But I also use PHP to generate parts of my stylesheets when it makes sense. Micha -- http://mfesser.de/blickwinkel
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.lang.php
csiph-web