Comments on: Call for input: Sandbox v0.8 http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/ Minimalism in blog design, an experiment Tue, 06 Jan 2009 23:18:39 +0000 By: Sandbox 0.9 Released @ 天佑的自由天地 http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2483 Sandbox 0.9 Released @ 天佑的自由天地 Tue, 29 May 2007 06:40:34 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2483 […] 這個版本在 markup 上當然有所改動，其中一些改動�?�從 Andy 在�?計 0.8 版本的改動內的留言略知一二，最清楚的方法莫�?�於自行細讀 zip file 內的 readme，或 Scott 放出來的 Sandbox 0.9 readme。 […] […] 這個版本在 markup 上當然有所改動，其中一些改動�?�從 Andy 在�?計 0.8 版本的改動內的留言略知一二，最清楚的方法莫�?�於自行細讀 zip file 內的 readme，或 Scott 放出來的 Sandbox 0.9 readme。 […]

]]> By: Sandbox v0.9 Released · plaintxt.org http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2482 Sandbox v0.9 Released · plaintxt.org Tue, 29 May 2007 05:55:43 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2482 [...] So what’s changed? Well, a great deal has. To get a taste you can read my comment in regards to the proposed 0.8 release. [...] [...] So what’s changed? Well, a great deal has. To get a taste you can read my comment in regards to the proposed 0.8 release. [...]

]]> By: Scott http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2481 Scott Wed, 16 May 2007 12:50:18 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2481 My text editor of choice is <a href="http://notepad-plus.sourceforge.net/" rel="nofollow">Notepad++</a>, though I often use <a href="http://www.newsgator.com/Individuals/TopStyle/" rel="nofollow">TopStyle Light</a> for hashing out CSS. I honestly don't care much for the full-fledged TopStyle program. My text editor of choice is Notepad++, though I often use TopStyle Light for hashing out CSS. I honestly don’t care much for the full-fledged TopStyle program.

]]> By: Ben http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2480 Ben Wed, 16 May 2007 10:51:58 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2480 Totally off topic, but what text editor are you using? Thanks, Ben Totally off topic, but what text editor are you using?

Thanks,
Ben

]]> By: Scott http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2479 Scott Mon, 14 May 2007 02:17:58 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2479 Hey Zeo. The whole <code>entry-author</code> is supposed to be just another hCard, and so just like any other hCard it <em>should</em> be in an <code>address</code> element, but it's not required (<a href="http://microformats.org/wiki/hatom#Entry_Author" rel="nofollow">link</a>). I did take your advice, Zeo, from an earlier comment you made about XOXO. You'll notice I've thrown in the <code>xoxo</code> class here and there. ;-) Hey Zeo.

The whole entry-author is supposed to be just another hCard, and so just like any other hCard it should be in an address element, but it’s not required (link).

I did take your advice, Zeo, from an earlier comment you made about XOXO. You’ll notice I’ve thrown in the xoxo class here and there. ;-)

]]> By: Zeo http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2478 Zeo Mon, 14 May 2007 01:18:28 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2478 I see xoxo :) Did you notice that it's required that Entry Author (hAtom) to be encoded with <code>address</code>. Anyway, right on time. Let me know when the new version is release. I see xoxo :)
Did you notice that it’s required that Entry Author (hAtom) to be encoded with address.

Anyway, right on time. Let me know when the new version is release.

]]> By: Scott http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2477 Scott Sat, 12 May 2007 18:05:55 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2477 Yes, maybe that's the best approach, <code>span.nav-meta</code>. One note on your previous comment, Adam: <code>body.single div.navigation</code> . I like to reuse selectors. ;-) Maybe even <code>div.navigation span.meta-sep</code>? Yes, maybe that’s the best approach, span.nav-meta. One note on your previous comment, Adam: body.single div.navigation . I like to reuse selectors. ;-)
Maybe even div.navigation span.meta-sep?

]]> By: adam http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2476 adam Sat, 12 May 2007 17:30:10 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2476 releases are good. SVN isn't complicated, but it sure sounds scary. :D meta-sep elements can be handled in CSS. the angled quotes can't. maybe they should have their own <code><span /></code>? releases are good. SVN isn’t complicated, but it sure sounds scary. :D
meta-sep elements can be handled in CSS. the angled quotes can’t. maybe they should have their own <span />?

]]> By: mackrick http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2475 mackrick Sat, 12 May 2007 16:38:16 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2475 It was my skin more than anything. Moving the skin css across messed up the header. I had extra menus in the title. Just removed the offending line from header.php and all was ok. Rick It was my skin more than anything. Moving the skin css across messed up the header. I had extra menus in the title. Just removed the offending line from header.php and all was ok.

Rick

]]> By: Scott http://www.plaintxt.org/2007/05/call-for-input-sandbox-v08/#comment-2474 Scott Sat, 12 May 2007 16:23:14 +0000 http://www.plaintxt.org/2007/05/09/call-for-input-sandbox-v08/#comment-2474 I think you're right, Adam. I did delete a few <code>&raquo;</code> (like in the submit button) but I'm hesitant to remove them all. I'm on the fence about them. If I zap those, then I really should zap the <code>meta-sep</code> elements. The <code>entry-author</code> was completely unnecessary. I decided to make all those 'post meta' classes more semantic and I really was out to trim as much fat as possible. I'm also going to make another class for trackback comments, eg, <code>t[n]</code>, for counting trackbacks. You'll see it in the readme.html, but it hasn't made its way to the theme files yet. Also, there's also <code>category-paged-[n]</code>, <code>date-paged-[n]</code>, etc., for paginated indexes. I've been reading up on hAtom, and I found out that if the <code>hfeed</code> element contains <code>rel="tag"</code> elements <em>outside</em> an hentry, then those are considered like category feed for the whole blog, semantically. I think that change is really promising. Also, I haven't bothered to update any of the skins yet, which I will do this weekend. Look for a release in the next few days. It's almost there. I have also removed most hardcoded <code>rel="me"</code>, because I read that they are implicit when pointing to a subdirectory. I think you’re right, Adam. I did delete a few &raquo; (like in the submit button) but I’m hesitant to remove them all. I’m on the fence about them. If I zap those, then I really should zap the meta-sep elements.

The entry-author was completely unnecessary. I decided to make all those ‘post meta’ classes more semantic and I really was out to trim as much fat as possible.

I’m also going to make another class for trackback comments, eg, t[n], for counting trackbacks. You’ll see it in the readme.html, but it hasn’t made its way to the theme files yet.

Also, there’s also category-paged-[n], date-paged-[n], etc., for paginated indexes.

I’ve been reading up on hAtom, and I found out that if the hfeed element contains rel="tag" elements outside an hentry, then those are considered like category feed for the whole blog, semantically. I think that change is really promising.

Also, I haven’t bothered to update any of the skins yet, which I will do this weekend. Look for a release in the next few days. It’s almost there.

I have also removed most hardcoded rel="me", because I read that they are implicit when pointing to a subdirectory.

]]>