<?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"
	>
<channel>
	<title>Comments for Simplish</title>
	<atom:link href="http://labs.utopian.net/blogs/simplish/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://labs.utopian.net/blogs/simplish</link>
	<description>Is a kind of Scribbish</description>
	<pubDate>Tue, 06 Jan 2009 08:58:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>Comment on Simplish version 2.1.4 by josh</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/12/12/simplish-214/#comment-1383</link>
		<dc:creator>josh</dc:creator>
		<pubDate>Mon, 15 Dec 2008 06:25:11 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=77#comment-1383</guid>
		<description>Note that when using "pretty" permalinks, threaded comments, and showing older comments first, you'll experience &lt;a href="http://trac.wordpress.org/ticket/8583" rel="nofollow"&gt;this bug originating in WordPress's comment template&lt;/a&gt; (i.e., &lt;em&gt;not&lt;/em&gt; a bug in Simplish). Comment permalinks on the first page of comments won't work.

A patch is available on the WordPress trac link above; or you can wait for WordPress 2.7.1 to get the official fix.</description>
		<content:encoded><![CDATA[<p>Note that when using &#8220;pretty&#8221; permalinks, threaded comments, and showing older comments first, you&#8217;ll experience <a href="http://trac.wordpress.org/ticket/8583" rel="nofollow">this bug originating in WordPress&#8217;s comment template</a> (i.e., <em>not</em> a bug in Simplish). Comment permalinks on the first page of comments won&#8217;t work.</p>
<p>A patch is available on the WordPress trac link above; or you can wait for WordPress 2.7.1 to get the official fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.1.3 by josh</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/11/27/simplish-213/#comment-1322</link>
		<dc:creator>josh</dc:creator>
		<pubDate>Fri, 12 Dec 2008 23:42:49 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=74#comment-1322</guid>
		<description>@Arthur: you can mail patches to josh@utopian.net -- while I have pretty &lt;code&gt;code&lt;/code&gt;, &lt;code&gt;pre&lt;/code&gt;, and &lt;code&gt;tt&lt;/code&gt; styles, I can't keep the php code from being munged out.

Mail 'em over and I'll take a look.</description>
		<content:encoded><![CDATA[<p>@Arthur: you can mail patches to <a href="mailto:josh@utopian.net">josh@utopian.net</a> &#8212; while I have pretty <code>code</code>, <code>pre</code>, and <code>tt</code> styles, I can&#8217;t keep the php code from being munged out.</p>
<p>Mail &#8216;em over and I&#8217;ll take a look.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.1.3 by Arthur</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/11/27/simplish-213/#comment-1321</link>
		<dc:creator>Arthur</dc:creator>
		<pubDate>Fri, 12 Dec 2008 23:35:13 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=74#comment-1321</guid>
		<description>(I think WP ate my code there... where do I send this to by e-mail?)</description>
		<content:encoded><![CDATA[<p>(I think WP ate my code there&#8230; where do I send this to by e-mail?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.1.3 by Arthur</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/11/27/simplish-213/#comment-1320</link>
		<dc:creator>Arthur</dc:creator>
		<pubDate>Fri, 12 Dec 2008 23:34:33 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=74#comment-1320</guid>
		<description>I'm a fan of 'grouping posts' by date, so for your consideration, which I do like this (main index template):

&lt;code&gt;

		


    &lt;!-- start changes --&gt;
	
	

             
			&#60;div id="article-" class="hentry"&#62;
			&#60;?php if ($new_post_time  $curr_post_time) { ?&#62;
                        
						
	&lt;!-- end changes --&gt;
	
	
&lt;/code&gt;

I use an extra H2 class. Additionally, hentryhead contains a condition to properly format the time for entries (no need to show date) when at WP's "homepage" ( is_home())  and use full dates+times  in other cases (see my website and click on a tag.).</description>
		<content:encoded><![CDATA[<p>I&#8217;m a fan of &#8216;grouping posts&#8217; by date, so for your consideration, which I do like this (main index template):</p>
<p><code></p>
<p>    <!-- start changes --></p>
<p>			&lt;div id=&#8221;article-&#8221; class=&#8221;hentry&#8221;&gt;<br />
			&lt;?php if ($new_post_time  $curr_post_time) { ?&gt;</p>
<p>	<!-- end changes --></p>
<p></code></p>
<p>I use an extra H2 class. Additionally, hentryhead contains a condition to properly format the time for entries (no need to show date) when at WP&#8217;s &#8220;homepage&#8221; ( is_home())  and use full dates+times  in other cases (see my website and click on a tag.).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.1.3 by Arthur</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/11/27/simplish-213/#comment-1274</link>
		<dc:creator>Arthur</dc:creator>
		<pubDate>Thu, 11 Dec 2008 03:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=74#comment-1274</guid>
		<description>(this is one of the themes that reads well on the iPod touch... Once again, thanks for the excellent theme)</description>
		<content:encoded><![CDATA[<p>(this is one of the themes that reads well on the iPod touch&#8230; Once again, thanks for the excellent theme)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.1.3 by Arthur</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/11/27/simplish-213/#comment-1273</link>
		<dc:creator>Arthur</dc:creator>
		<pubDate>Thu, 11 Dec 2008 03:17:07 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=74#comment-1273</guid>
		<description>Excellent theme. Thanks for keeping the layout simple.</description>
		<content:encoded><![CDATA[<p>Excellent theme. Thanks for keeping the layout simple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Not about JavaScript by josh</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/11/15/not-about-javascript/#comment-1045</link>
		<dc:creator>josh</dc:creator>
		<pubDate>Sat, 29 Nov 2008 03:44:05 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=69#comment-1045</guid>
		<description>Aha! Thank you for the tip - important for doing stuff on other instances than a single post.</description>
		<content:encoded><![CDATA[<p>Aha! Thank you for the tip - important for doing stuff on other instances than a single post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Not about JavaScript by Otto</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/11/15/not-about-javascript/#comment-1037</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Fri, 28 Nov 2008 18:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=69#comment-1037</guid>
		<description>No, is_singular() was correct. It's a function that returns the variable (much like all the other is_whatever() functions). 

is_singular() returns true on single posts, pages, and attachments. This is just slightly different from is_single().</description>
		<content:encoded><![CDATA[<p>No, is_singular() was correct. It&#8217;s a function that returns the variable (much like all the other is_whatever() functions). </p>
<p>is_singular() returns true on single posts, pages, and attachments. This is just slightly different from is_single().</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Threadbare no longer (Simplish 2.1.4RC) by Simplish version 2.1.3 - Simplish</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/11/27/threadbare-no-longer-simplish-214rc/#comment-1022</link>
		<dc:creator>Simplish version 2.1.3 - Simplish</dc:creator>
		<pubDate>Thu, 27 Nov 2008 21:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=75#comment-1022</guid>
		<description>[...] should be using on your real site, you know, where you don&#8217;t run pre-release software like Simplish 2.1.4RC, or WordPress [...]</description>
		<content:encoded><![CDATA[<p>[...] should be using on your real site, you know, where you don&#8217;t run pre-release software like Simplish 2.1.4RC, or WordPress [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Threadbare no longer (Simplish 2.1.4RC) by josh</title>
		<link>http://labs.utopian.net/blogs/simplish/dev/2008/11/27/threadbare-no-longer-simplish-214rc/#comment-1020</link>
		<dc:creator>josh</dc:creator>
		<pubDate>Thu, 27 Nov 2008 20:30:05 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=75#comment-1020</guid>
		<description>Another bug I've already noticed is that &lt;a href="http://labs.utopian.net/who/josh/wp-svn/?p=1&#38;cpage=1#comment-18" rel="nofollow"&gt;(ping track)^back handling is weak -- and rather ugly&lt;/a&gt;. A general CSS cleanup and re-sync with changed tags, ids, and classes will happen before release.

I resist splitting comments from pingbacks as do lots of other themes, because I think &lt;em&gt;ideally&lt;/em&gt; the two response forms should be the same kind of communication, merely being sent via two (very slightly) different media.</description>
		<content:encoded><![CDATA[<p>Another bug I&#8217;ve already noticed is that <a href="http://labs.utopian.net/who/josh/wp-svn/?p=1&amp;cpage=1#comment-18" rel="nofollow">(ping track)^back handling is weak &#8212; and rather ugly</a>. A general CSS cleanup and re-sync with changed tags, ids, and classes will happen before release.</p>
<p>I resist splitting comments from pingbacks as do lots of other themes, because I think <em>ideally</em> the two response forms should be the same kind of communication, merely being sent via two (very slightly) different media.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
