<?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 for The WordPress Community</title>
	<atom:link href="http://wp-community.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://wp-community.org</link>
	<description>Home of the #1 podcast for WordPress-related news, tips and information</description>
	<pubDate>Sat, 04 Jul 2009 12:27:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Episode 50: WordPress 2.7.1 released, WordPress.tv, How much do YOU love WordPress? by Simon Jones</title>
		<link>http://wp-community.org/2009/03/02/episode-50-wordpress-271-released-wordpresstv-how-much-do-you-love-wordpress/comment-page-1/#comment-3078</link>
		<dc:creator>Simon Jones</dc:creator>
		<pubDate>Wed, 11 Mar 2009 10:54:09 +0000</pubDate>
		<guid isPermaLink="false">http://wp-community.org/?p=321#comment-3078</guid>
		<description>Yay you got rid of the bloody hidious guitar theme music! Thank God! :-)</description>
		<content:encoded><![CDATA[<p>Yay you got rid of the bloody hidious guitar theme music! Thank God! <img src='http://wp-community.org/wp/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Episode 50: WordPress 2.7.1 released, WordPress.tv, How much do YOU love WordPress? by Doc Rock</title>
		<link>http://wp-community.org/2009/03/02/episode-50-wordpress-271-released-wordpresstv-how-much-do-you-love-wordpress/comment-page-1/#comment-3070</link>
		<dc:creator>Doc Rock</dc:creator>
		<pubDate>Sat, 07 Mar 2009 12:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://wp-community.org/?p=321#comment-3070</guid>
		<description>It is good to have you back.  TWPC podcast is by far the best and i was jonesin while you guys were gone.  Keep up the good work.  Aloha

Doc</description>
		<content:encoded><![CDATA[<p>It is good to have you back.  TWPC podcast is by far the best and i was jonesin while you guys were gone.  Keep up the good work.  Aloha</p>
<p>Doc</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Episode 50: WordPress 2.7.1 released, WordPress.tv, How much do YOU love WordPress? by Kyle</title>
		<link>http://wp-community.org/2009/03/02/episode-50-wordpress-271-released-wordpresstv-how-much-do-you-love-wordpress/comment-page-1/#comment-3067</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Wed, 04 Mar 2009 16:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://wp-community.org/?p=321#comment-3067</guid>
		<description>Regarding Fred's question -- you could use a differencing utility, like kdiff3 to what the changes are prior to installing (I haven't yet had a customization "bump heads" with developer's changes) but I say that's the wrong answer. Fred mentioned that he's consolidating his style sheet calls (presumably .js as well) to reduce the number of requests a page makes. There's a plugin that does this for you automatically. I'd say it if I knew it but you can google as well as I can. (I think I saw it mentioned on NETTUTS.com) I don't think it buys that much performance gain for sites of the scope we develop) BUT it let's you aggregate your css/js calls WITHOUT your having to do so by hand. 

So you get what you want without having to tear into plugin code.

Thanks for a great podcast!</description>
		<content:encoded><![CDATA[<p>Regarding Fred&#8217;s question &#8212; you could use a differencing utility, like kdiff3 to what the changes are prior to installing (I haven&#8217;t yet had a customization &#8220;bump heads&#8221; with developer&#8217;s changes) but I say that&#8217;s the wrong answer. Fred mentioned that he&#8217;s consolidating his style sheet calls (presumably .js as well) to reduce the number of requests a page makes. There&#8217;s a plugin that does this for you automatically. I&#8217;d say it if I knew it but you can google as well as I can. (I think I saw it mentioned on NETTUTS.com) I don&#8217;t think it buys that much performance gain for sites of the scope we develop) BUT it let&#8217;s you aggregate your css/js calls WITHOUT your having to do so by hand. </p>
<p>So you get what you want without having to tear into plugin code.</p>
<p>Thanks for a great podcast!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Episode 50: WordPress 2.7.1 released, WordPress.tv, How much do YOU love WordPress? by Nicolas</title>
		<link>http://wp-community.org/2009/03/02/episode-50-wordpress-271-released-wordpresstv-how-much-do-you-love-wordpress/comment-page-1/#comment-3063</link>
		<dc:creator>Nicolas</dc:creator>
		<pubDate>Tue, 03 Mar 2009 07:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://wp-community.org/?p=321#comment-3063</guid>
		<description>What you were talking about those Plugin's is actually already possible with at least one I know about ... it's the CFormsII (Contact Form Plugin). There you can place our custom Contact Form CSS file in a subfolder of the Plugins folder calles custom-cforms and it's going to stay there even if the Plugin get's an update. Maybe something like this would be possible for other things as well.

Good to hear you're back on ... keep the episodes coming!</description>
		<content:encoded><![CDATA[<p>What you were talking about those Plugin&#8217;s is actually already possible with at least one I know about &#8230; it&#8217;s the CFormsII (Contact Form Plugin). There you can place our custom Contact Form CSS file in a subfolder of the Plugins folder calles custom-cforms and it&#8217;s going to stay there even if the Plugin get&#8217;s an update. Maybe something like this would be possible for other things as well.</p>
<p>Good to hear you&#8217;re back on &#8230; keep the episodes coming!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Episode 49: WordPress 2.7 released, Oxite, Blog World Expo and New Media Expo to merge, Pownce closes by WordPress News: WordPress.tv, WordCamp Whistler, WordPress Logo, City Saves Money, and More &#124; The Blog Herald</title>
		<link>http://wp-community.org/2008/12/30/episode-49-wordpress-27-released-oxite-blog-world-expo-and-new-media-expo-to-merge-pownce-closes/comment-page-1/#comment-3030</link>
		<dc:creator>WordPress News: WordPress.tv, WordCamp Whistler, WordPress Logo, City Saves Money, and More &#124; The Blog Herald</dc:creator>
		<pubDate>Fri, 23 Jan 2009 06:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://wp-community.org/?p=309#comment-3030</guid>
		<description>[...] WordPress Podcast: Episode 49: WordPress 2.7 released, Oxite, Blog World Expo and New Media Expo to merge, Pownce close... is the latest [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress Podcast: Episode 49: WordPress 2.7 released, Oxite, Blog World Expo and New Media Expo to merge, Pownce close&#8230; is the latest [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
