Comments on: Threadbare no longer (Simplish 2.1.4RC) http://simplish.pomfolio.com/dev/2008/11/27/threadbare-no-longer-simplish-214rc/ is a kind of Scribbish Wed, 26 Jan 2011 00:04:29 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Simplish version 2.1.3 - Simplish http://simplish.pomfolio.com/dev/2008/11/27/threadbare-no-longer-simplish-214rc/comment-page-1/#comment-40 Simplish version 2.1.3 - Simplish Thu, 27 Nov 2008 21:45:45 +0000 http://labs.utopian.net/blogs/simplish/?p=75#comment-40 [...] should be using on your real site, you know, where you don’t run pre-release software like Simplish 2.1.4RC, or WordPress [...] [...] should be using on your real site, you know, where you don’t run pre-release software like Simplish 2.1.4RC, or WordPress [...]

]]> By: josh http://simplish.pomfolio.com/dev/2008/11/27/threadbare-no-longer-simplish-214rc/comment-page-1/#comment-41 josh Thu, 27 Nov 2008 20:30:05 +0000 http://labs.utopian.net/blogs/simplish/?p=75#comment-41 Another bug I've already noticed is that <a href="http://labs.utopian.net/who/josh/wp-svn/?p=1&cpage=1#comment-18" rel="nofollow">(ping track)^back handling is weak -- and rather ugly</a>. 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 <em>ideally</em> the two response forms should be the same kind of communication, merely being sent via two (very slightly) different media. Another bug I’ve already noticed is that (ping track)^back handling is weak — and rather ugly. 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 ideally the two response forms should be the same kind of communication, merely being sent via two (very slightly) different media.

]]>