<?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 symfony plugin with LESS</title>
	<atom:link href="http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/</link>
	<description>VPS &#38; Shared Hosting, symfony, Zend Framework, Rails, Adobe Flex, Hosting News, Web Design Tips, Webhosting and more....</description>
	<lastBuildDate>Tue, 31 Aug 2010 19:34:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: ServerGrove Web Hosting Blog &#187; Blog Archive &#187; Tips for configuring CSS in symfony</title>
		<link>http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/comment-page-1/#comment-1110</link>
		<dc:creator>ServerGrove Web Hosting Blog &#187; Blog Archive &#187; Tips for configuring CSS in symfony</dc:creator>
		<pubDate>Wed, 09 Sep 2009 17:09:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servergrove.com/?p=493#comment-1110</guid>
		<description>[...] Previously in this blog we talked about LESS and how it can help working with extended features in CSS. But some basic things with configuring CSS in symfony are commonly unknown. [...]</description>
		<content:encoded><![CDATA[<p>[...] Previously in this blog we talked about LESS and how it can help working with extended features in CSS. But some basic things with configuring CSS in symfony are commonly unknown. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/comment-page-1/#comment-990</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Wed, 05 Aug 2009 14:50:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servergrove.com/?p=493#comment-990</guid>
		<description>sjoerd - asking them to use the sf prefix for their plugin is like complaining about java developers using their own namespaces for their classes.

It makes a LOT of sense for each developer to use their own plugin prefix so that they don&#039;t run the risk of clashing plugin names.</description>
		<content:encoded><![CDATA[<p>sjoerd &#8211; asking them to use the sf prefix for their plugin is like complaining about java developers using their own namespaces for their classes.</p>
<p>It makes a LOT of sense for each developer to use their own plugin prefix so that they don&#8217;t run the risk of clashing plugin names.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pablo</title>
		<link>http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/comment-page-1/#comment-983</link>
		<dc:creator>Pablo</dc:creator>
		<pubDate>Sat, 01 Aug 2009 16:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servergrove.com/?p=493#comment-983</guid>
		<description>@glenn

We are not familiar with Compass, but from what it looks like, it is a CSS framework and uses the Saas syntax which is a bit different than LESS. We liked LESS syntax because it is close to standard CSS.</description>
		<content:encoded><![CDATA[<p>@glenn</p>
<p>We are not familiar with Compass, but from what it looks like, it is a CSS framework and uses the Saas syntax which is a bit different than LESS. We liked LESS syntax because it is close to standard CSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pablo</title>
		<link>http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/comment-page-1/#comment-982</link>
		<dc:creator>Pablo</dc:creator>
		<pubDate>Sat, 01 Aug 2009 16:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servergrove.com/?p=493#comment-982</guid>
		<description>@sjoerd

There has been a lot of discussion about naming plugins, and from what we understand, sf prefix is reserved for official plugins and it is recommended to use the prefix to identify the author of the plugin and avoid conflicts in names. We don&#039;t look for people to remember us when using the plugin, and we feel it does not make things harder. If you look around there are plenty of plugins with special prefixes. thanks for your comment!</description>
		<content:encoded><![CDATA[<p>@sjoerd</p>
<p>There has been a lot of discussion about naming plugins, and from what we understand, sf prefix is reserved for official plugins and it is recommended to use the prefix to identify the author of the plugin and avoid conflicts in names. We don&#8217;t look for people to remember us when using the plugin, and we feel it does not make things harder. If you look around there are plenty of plugins with special prefixes. thanks for your comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vince</title>
		<link>http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/comment-page-1/#comment-980</link>
		<dc:creator>vince</dc:creator>
		<pubDate>Sat, 01 Aug 2009 15:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servergrove.com/?p=493#comment-980</guid>
		<description>Really nice to discover LESS
That&#039;s the kind of stuff we all need every day.
Nice to turn it into a plugin, will definitely try it out !

:)</description>
		<content:encoded><![CDATA[<p>Really nice to discover LESS<br />
That&#8217;s the kind of stuff we all need every day.<br />
Nice to turn it into a plugin, will definitely try it out !</p>
<p>:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sjoerd</title>
		<link>http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/comment-page-1/#comment-979</link>
		<dc:creator>sjoerd</dc:creator>
		<pubDate>Sat, 01 Aug 2009 07:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servergrove.com/?p=493#comment-979</guid>
		<description>Hey,

Very nice work of both your team and the LESS team!! I wonder though why the plugin is not named sfLESS or something?
Using all these custom prefixes makes it harder to code, as you always have to remember who made the plugin and what prefix to use. Is it really important to you I think of servergrove when using this plugin? Please serve the community and supply a sfLESS plugin...

Regards,
 Sjoerd</description>
		<content:encoded><![CDATA[<p>Hey,</p>
<p>Very nice work of both your team and the LESS team!! I wonder though why the plugin is not named sfLESS or something?<br />
Using all these custom prefixes makes it harder to code, as you always have to remember who made the plugin and what prefix to use. Is it really important to you I think of servergrove when using this plugin? Please serve the community and supply a sfLESS plugin&#8230;</p>
<p>Regards,<br />
 Sjoerd</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glenn McLelland</title>
		<link>http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/comment-page-1/#comment-975</link>
		<dc:creator>Glenn McLelland</dc:creator>
		<pubDate>Fri, 31 Jul 2009 19:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servergrove.com/?p=493#comment-975</guid>
		<description>What about Compass?  How does it compare with Less?

http://wiki.github.com/chriseppstein/compass</description>
		<content:encoded><![CDATA[<p>What about Compass?  How does it compare with Less?</p>
<p><a href="http://wiki.github.com/chriseppstein/compass" rel="nofollow">http://wiki.github.com/chriseppstein/compass</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tonio</title>
		<link>http://blog.servergrove.com/2009/07/30/css-symfony-plugin-with-lessphp/comment-page-1/#comment-954</link>
		<dc:creator>Tonio</dc:creator>
		<pubDate>Fri, 31 Jul 2009 08:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servergrove.com/?p=493#comment-954</guid>
		<description>Hey,

You&#039;re fast :)</description>
		<content:encoded><![CDATA[<p>Hey,</p>
<p>You&#8217;re fast :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
