<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: CSS abstraction made simple with PHP</title>
	<atom:link href="http://www.position-absolute.com/news/css-abstraction-made-simple-with-php/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.position-absolute.com/news/css-abstraction-made-simple-with-php/</link>
	<description>Get your web worker news fix</description>
	<lastBuildDate>Fri, 10 Feb 2012 21:12:55 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Eppstein</title>
		<link>http://www.position-absolute.com/news/css-abstraction-made-simple-with-php/comment-page-1/#comment-3160</link>
		<dc:creator>Chris Eppstein</dc:creator>
		<pubDate>Thu, 01 Oct 2009 20:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1719#comment-3160</guid>
		<description>@cedric
Point taken about caching. You really should check out CSScaffold. It is written in PHP and is very full featured. http://github.com/anthonyshort/csscaffold

lesscss and sass are both written in ruby, neither requires you to have ruby on your production systems, just your dev and build systems and none require you to know how to write ruby code. Your machines probably have it installed already, and if they don&#039;t, it&#039;s easy to install.</description>
		<content:encoded><![CDATA[<p>@cedric<br />
Point taken about caching. You really should check out CSScaffold. It is written in PHP and is very full featured. <a href="http://github.com/anthonyshort/csscaffold" rel="nofollow">http://github.com/anthonyshort/csscaffold</a></p>
<p>lesscss and sass are both written in ruby, neither requires you to have ruby on your production systems, just your dev and build systems and none require you to know how to write ruby code. Your machines probably have it installed already, and if they don&#8217;t, it&#8217;s easy to install.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cedric Dugas</title>
		<link>http://www.position-absolute.com/news/css-abstraction-made-simple-with-php/comment-page-1/#comment-3159</link>
		<dc:creator>Cedric Dugas</dc:creator>
		<pubDate>Thu, 01 Oct 2009 16:35:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1719#comment-3159</guid>
		<description>@Chris serving CSS as php is not an issue if you are using a caching system for php files, which most server use. 

All imported css file should be converted in 1 one file anyway, lots of framework have an option for this, so this is a not really an issue, for me anyway

As for sass and compass, I do not use ruby, most company I know do not use it (and by this I mean it is not really a popular framework in my city). Less css is another good option, still need to install software on the server. I still think there is a place for php in this, if well executed.

But I agree that a full featured PHP abstraction would need a word of warning about how it is parsed on the server.</description>
		<content:encoded><![CDATA[<p>@Chris serving CSS as php is not an issue if you are using a caching system for php files, which most server use. </p>
<p>All imported css file should be converted in 1 one file anyway, lots of framework have an option for this, so this is a not really an issue, for me anyway</p>
<p>As for sass and compass, I do not use ruby, most company I know do not use it (and by this I mean it is not really a popular framework in my city). Less css is another good option, still need to install software on the server. I still think there is a place for php in this, if well executed.</p>
<p>But I agree that a full featured PHP abstraction would need a word of warning about how it is parsed on the server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Eppstein</title>
		<link>http://www.position-absolute.com/news/css-abstraction-made-simple-with-php/comment-page-1/#comment-3158</link>
		<dc:creator>Chris Eppstein</dc:creator>
		<pubDate>Thu, 01 Oct 2009 16:20:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1719#comment-3158</guid>
		<description>@ehecatl What is not user friendly about sass and compass?

@cedric There are performance reasons why serving php templated css that never changes per user is a bad thing to encourage (or not even warn people about).

If you&#039;re looking for a more familiar syntax, you should check out http://lesscss.org/

It&#039;s true that you can achieve many of the abstraction benefits that my article points out with php, but dedicated css syntaxes like sass and less (and for php users: csscaffold) really up the level of expressiveness and maintainability of the stylesheets in lots of small ways that add up.</description>
		<content:encoded><![CDATA[<p>@ehecatl What is not user friendly about sass and compass?</p>
<p>@cedric There are performance reasons why serving php templated css that never changes per user is a bad thing to encourage (or not even warn people about).</p>
<p>If you&#8217;re looking for a more familiar syntax, you should check out <a href="http://lesscss.org/" rel="nofollow">http://lesscss.org/</a></p>
<p>It&#8217;s true that you can achieve many of the abstraction benefits that my article points out with php, but dedicated css syntaxes like sass and less (and for php users: csscaffold) really up the level of expressiveness and maintainability of the stylesheets in lots of small ways that add up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ehecatl Mendoza</title>
		<link>http://www.position-absolute.com/news/css-abstraction-made-simple-with-php/comment-page-1/#comment-3157</link>
		<dc:creator>Ehecatl Mendoza</dc:creator>
		<pubDate>Thu, 01 Oct 2009 13:34:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1719#comment-3157</guid>
		<description>So simple and so useful!
I know compass is already doing this, but its no easy to get started and understand by common designers.
I really think that your approach will fit better on actual web design agencies workflow. Lets wait Sass and Compass evolve a little more until they are really user friendly.</description>
		<content:encoded><![CDATA[<p>So simple and so useful!<br />
I know compass is already doing this, but its no easy to get started and understand by common designers.<br />
I really think that your approach will fit better on actual web design agencies workflow. Lets wait Sass and Compass evolve a little more until they are really user friendly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cedric Dugas</title>
		<link>http://www.position-absolute.com/news/css-abstraction-made-simple-with-php/comment-page-1/#comment-3156</link>
		<dc:creator>Cedric Dugas</dc:creator>
		<pubDate>Thu, 01 Oct 2009 12:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1719#comment-3156</guid>
		<description>I completely understand your point,  you are talking of taking CSS to a new level and this is really great but,

Still  I think abstraction trough php can have its place, it will certainly not be as powerful as mixins, because it do not understand the context of the whole selector. But it is a possible middle ground. 

Of course the bigger benefit is that this solution is ready to go, no installation needed on the server.</description>
		<content:encoded><![CDATA[<p>I completely understand your point,  you are talking of taking CSS to a new level and this is really great but,</p>
<p>Still  I think abstraction trough php can have its place, it will certainly not be as powerful as mixins, because it do not understand the context of the whole selector. But it is a possible middle ground. </p>
<p>Of course the bigger benefit is that this solution is ready to go, no installation needed on the server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Eppstein</title>
		<link>http://www.position-absolute.com/news/css-abstraction-made-simple-with-php/comment-page-1/#comment-3148</link>
		<dc:creator>Chris Eppstein</dc:creator>
		<pubDate>Thu, 01 Oct 2009 07:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1719#comment-3148</guid>
		<description>Someone asked on my blog why not just use ERB (the ruby equivalent of passing css thru php) instead of Sass to achieve the same result. Why introduce a whole new language? My reply applies here as well:

http://chriseppstein.github.com/blog/2009/09/20/why-stylesheet-abstraction-matters/#comment-17898982

Additionally, I didn&#039;t demonstrate the full power of mixins in my original post, but you simply cannot achieve the same results using this kind of templating approach as you can with mixins, because mixins know the selector context they are being mixed into, this allows you to embed nested selectors into the calling context.</description>
		<content:encoded><![CDATA[<p>Someone asked on my blog why not just use ERB (the ruby equivalent of passing css thru php) instead of Sass to achieve the same result. Why introduce a whole new language? My reply applies here as well:</p>
<p><a href="http://chriseppstein.github.com/blog/2009/09/20/why-stylesheet-abstraction-matters/#comment-17898982" rel="nofollow">http://chriseppstein.github.com/blog/2009/09/20/why-stylesheet-abstraction-matters/#comment-17898982</a></p>
<p>Additionally, I didn&#8217;t demonstrate the full power of mixins in my original post, but you simply cannot achieve the same results using this kind of templating approach as you can with mixins, because mixins know the selector context they are being mixed into, this allows you to embed nested selectors into the calling context.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

