Re: Parsing .css files with php: Cons? [message #176744 is a reply to message #176743] |
Sat, 21 January 2012 07:10 |
J.O. Aho
Messages: 194 Registered: September 2010
Karma:
|
Senior Member |
|
|
Chuck Anderson wrote:
> Michael Fesser wrote:
>> .oO(Captain Paralytic)
>>
>>> On Jan 20, 10:25 am, Michael Fesser <neti...@gmx.de> wrote:
>>>> No. You have to explicitly send the correct header or some browsers
>>>> might ignore the CSS. For example
>>>>
>>>> header('Content-Type: text/css; charset=UTF-8')
>>> Oh OK. Any ideas which ones?
>>
>> In the past Gecko browsers (i.e. Firefox) were a bit picky about the
>> correct CSS content type. If the file wasn't delivered as text/css, it
>> was ignored.
>>
> I have successfully used:
> header("Content-type: text/css");
>
> After implementing a php based style sheet a couple of different times it
> seemed wasteful, and a bit of a kludge. If the style sheet is ultimately
> static, it is wasteful to keep generating one every time it is used. Now I use
> a php script to generate the style sheet file for me. If I want to make
> changes I edit the php based file (or any included definition files, e.g.,
> colors.php) and run it.
>
I have to say it feels quite much of extra work, writing the php script which
generates the css, as you need to edit the php file, then IMHO you can quite
easily edit a css instead. I could see a bit more point of your script if you
have a database as a backend, where you store the values and recreate the css
each time the values change.
--
//Aho
|
|
|