<?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: Serving JavaScript and CSS</title>
	<atom:link href="http://naneau.nl/2007/05/28/serving-javascript-and-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://naneau.nl/2007/05/28/serving-javascript-and-css/</link>
	<description>Go dik-dik, go!</description>
	<lastBuildDate>Fri, 03 Sep 2010 14:00:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ultram.</title>
		<link>http://naneau.nl/2007/05/28/serving-javascript-and-css/comment-page-1/#comment-99547</link>
		<dc:creator>Ultram.</dc:creator>
		<pubDate>Mon, 15 Feb 2010 00:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://naneau.nl/2007/05/28/serving-javascript-and-css/#comment-99547</guid>
		<description>&lt;strong&gt;Ultram....&lt;/strong&gt;

Ultram. Generic ultram....</description>
		<content:encoded><![CDATA[<p><strong>Ultram&#8230;.</strong></p>
<p>Ultram. Generic ultram&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Naneau</title>
		<link>http://naneau.nl/2007/05/28/serving-javascript-and-css/comment-page-1/#comment-337</link>
		<dc:creator>Naneau</dc:creator>
		<pubDate>Sun, 03 Jun 2007 10:44:51 +0000</pubDate>
		<guid isPermaLink="false">http://naneau.nl/2007/05/28/serving-javascript-and-css/#comment-337</guid>
		<description>AlesL is of course absolutely right. I included the packing as a bit of an afterthought, and didn&#039;t feel like editing the respective files (csstidy, while functional, could do with some phpdoc as well).

If you really require E_STRICT compatibility, I would suggest you follow AlesL&#039;s suggestions, or leave the packing out all together.</description>
		<content:encoded><![CDATA[<p>AlesL is of course absolutely right. I included the packing as a bit of an afterthought, and didn&#8217;t feel like editing the respective files (csstidy, while functional, could do with some phpdoc as well).</p>
<p>If you really require E_STRICT compatibility, I would suggest you follow AlesL&#8217;s suggestions, or leave the packing out all together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlesL</title>
		<link>http://naneau.nl/2007/05/28/serving-javascript-and-css/comment-page-1/#comment-329</link>
		<dc:creator>AlesL</dc:creator>
		<pubDate>Sat, 02 Jun 2007 21:26:15 +0000</pubDate>
		<guid isPermaLink="false">http://naneau.nl/2007/05/28/serving-javascript-and-css/#comment-329</guid>
		<description>Cool!

Just one notice:
ZF Requires E_STRICT compatibility so optimizing css with CSSTidy throws a bunch of Strict Standards lines:
Non-static method csstidy::is_important() ...

Add litlle hacking in class.csstidy_optimise.php file!

Adding static to these two functions solves the problem!
static function is_important($value)
static function gvw_important($value)

Regards,
AlesL</description>
		<content:encoded><![CDATA[<p>Cool!</p>
<p>Just one notice:<br />
ZF Requires E_STRICT compatibility so optimizing css with CSSTidy throws a bunch of Strict Standards lines:<br />
Non-static method csstidy::is_important() &#8230;</p>
<p>Add litlle hacking in class.csstidy_optimise.php file!</p>
<p>Adding static to these two functions solves the problem!<br />
static function is_important($value)<br />
static function gvw_important($value)</p>
<p>Regards,<br />
AlesL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Lee</title>
		<link>http://naneau.nl/2007/05/28/serving-javascript-and-css/comment-page-1/#comment-238</link>
		<dc:creator>Patrick Lee</dc:creator>
		<pubDate>Mon, 28 May 2007 14:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://naneau.nl/2007/05/28/serving-javascript-and-css/#comment-238</guid>
		<description>Great post.  I also fret about optimizing my JS and CSS files though I haven&#039;t delved into the many compression possibilities.  Not sure about you, but I find it very surprising that Prototype leaves out some semicolons.  Don&#039;t they know that people will try to compress and/or pack it?</description>
		<content:encoded><![CDATA[<p>Great post.  I also fret about optimizing my JS and CSS files though I haven&#8217;t delved into the many compression possibilities.  Not sure about you, but I find it very surprising that Prototype leaves out some semicolons.  Don&#8217;t they know that people will try to compress and/or pack it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
