Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.php > #4554

Re: Parsing .css files with php: Cons?

Path csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From "J.O. Aho" <user@example.net>
Newsgroups comp.lang.php
Subject Re: Parsing .css files with php: Cons?
Date Sat, 21 Jan 2012 08:10:28 +0100
Lines 36
Message-ID <9nv6n4F6anU1@mid.individual.net> (permalink)
References <400f69e3-9555-4cc0-b529-6dbca54d9bfa@k3g2000pbn.googlegroups.com> <a24408e9-1d0e-4fda-b38a-c9b63fab69fd@p4g2000vbt.googlegroups.com> <c60e98fb-abdf-495e-8df5-18cf66a303ec@v6g2000pba.googlegroups.com> <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>
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 7bit
X-Trace individual.net fE1wdkcdcyJCMEorIZj+yw40J0ctWY4BWBMCNp6H1w8zONC0pR
Cancel-Lock sha1:i4bT9iy53n8ZBVGhQeiZeouHt9E=
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20111226 Firefox/9.0.1 SeaMonkey/2.6.1
In-Reply-To <jfd5l1$cmc$1@dont-email.me>
Xref x330-a1.tempe.blueboxinc.net comp.lang.php:4554

Show key headers only | View raw


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

Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


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