<?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: User Interface Nitpick: Forward or Back?</title>
	<atom:link href="http://www.bloggingpro.com/archives/2006/06/07/1317/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloggingpro.com/archives/2006/06/07/1317/</link>
	<description>News, plugins and themes for blogging applications</description>
	<lastBuildDate>Thu, 09 Feb 2012 19:29:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: tÃ¼tÃ¼ne son</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-243237</link>
		<dc:creator>tÃ¼tÃ¼ne son</dc:creator>
		<pubDate>Sun, 06 Feb 2011 11:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-243237</guid>
		<description>Frankly? Iâ€™ve landed on page two of this blog and been completely confused by the page navigation. hee.. I agree with Nick, that in my mind â€œpreviousâ€ calls to mind something that happened in the past while â€œnextâ€ refers to more future events. :)</description>
		<content:encoded><![CDATA[<p>Frankly? Iâ€™ve landed on page two of this blog and been completely confused by the page navigation. hee.. I agree with Nick, that in my mind â€œpreviousâ€ calls to mind something that happened in the past while â€œnextâ€ refers to more future events. <img src='http://www.bloggingpro.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sohbet</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-214266</link>
		<dc:creator>sohbet</dc:creator>
		<pubDate>Wed, 23 Jul 2008 19:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-214266</guid>
		<description>I like to use previous/next in reference to date/time because this is what blogging really revolves around</description>
		<content:encoded><![CDATA[<p>I like to use previous/next in reference to date/time because this is what blogging really revolves around</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: milo</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-80861</link>
		<dc:creator>milo</dc:creator>
		<pubDate>Wed, 15 Nov 2006 07:27:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-80861</guid>
		<description>I made it like this:
&#124; Top &#124; Â« Previous Entries &#124; Next Entries Â» &#124; Home Â» Page 2 &#124;
with breadcrumb built in, it works ok, i think.</description>
		<content:encoded><![CDATA[<p>I made it like this:<br />
| Top | Â« Previous Entries | Next Entries Â» | Home Â» Page 2 |<br />
with breadcrumb built in, it works ok, i think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#160; Matt Mullenweg&#8217;s New Design&#160;by&#160;Blogging Pro</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-79823</link>
		<dc:creator>&#160; Matt Mullenweg&#8217;s New Design&#160;by&#160;Blogging Pro</dc:creator>
		<pubDate>Tue, 14 Nov 2006 03:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-79823</guid>
		<description>[...] Also, there are little things that bug me. One thing that is pretty much universal for me is when people use next page to go to page two instead of previous page. I don&#8217;t know why it bugs me, but it really does. I have commented about the previous/next issue before on BloggingPro.   Tags: [...]</description>
		<content:encoded><![CDATA[<p>[...] Also, there are little things that bug me. One thing that is pretty much universal for me is when people use next page to go to page two instead of previous page. I don&#8217;t know why it bugs me, but it really does. I have commented about the previous/next issue before on BloggingPro.   Tags: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quake Cake</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-74960</link>
		<dc:creator>Quake Cake</dc:creator>
		<pubDate>Mon, 06 Nov 2006 22:49:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-74960</guid>
		<description>God bless this world</description>
		<content:encoded><![CDATA[<p>God bless this world</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Egor Kurg</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-55995</link>
		<dc:creator>Egor Kurg</dc:creator>
		<pubDate>Wed, 11 Oct 2006 19:17:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-55995</guid>
		<description>Thank you very very very much. Wish you luck and mercy from all the creatures around the world.</description>
		<content:encoded><![CDATA[<p>Thank you very very very much. Wish you luck and mercy from all the creatures around the world.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-25362</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 12 Jun 2006 14:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-25362</guid>
		<description>Actually Chris, I like that idea. There would be no previous and next confusion if we went towards Older Entries and Newer Entries. 

I think that many blogs still think of their first page as the first page of a book, making next go to page two, and previous go to page one. This does not seem to be the majority though.</description>
		<content:encoded><![CDATA[<p>Actually Chris, I like that idea. There would be no previous and next confusion if we went towards Older Entries and Newer Entries. </p>
<p>I think that many blogs still think of their first page as the first page of a book, making next go to page two, and previous go to page one. This does not seem to be the majority though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Meller</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24901</link>
		<dc:creator>Chris Meller</dc:creator>
		<pubDate>Fri, 09 Jun 2006 15:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24901</guid>
		<description>This is just like aruging whether turning the A/C up makes it colder or warmer in the room...

On the one hand, if you turn it up, it puts out more cold air, making the room cooler; but in fact you&#039;re turning it down on the dial...

But on the other hand, if you turn it up, relative to degrees on the dial, you&#039;re going to make it warmer in the room.

I say previous is previous. It&#039;s the past. Relative to where you are now, the previous things in life are those that are older. If I click a link that says &#039;Previous Entries&#039;, I expect those from the past - the older ones. &#039;Next Entries&#039; really isn&#039;t particularly descriptive in my mind, but if it&#039;s not a previous entry, what is it? Obviously in this case, if you put 2 and 2 together, next would mean newer.

Or we could just standardize the whole thing with &quot;Older Entries&quot; and &quot;Newer Entries&quot; and be done with it.</description>
		<content:encoded><![CDATA[<p>This is just like aruging whether turning the A/C up makes it colder or warmer in the room&#8230;</p>
<p>On the one hand, if you turn it up, it puts out more cold air, making the room cooler; but in fact you&#8217;re turning it down on the dial&#8230;</p>
<p>But on the other hand, if you turn it up, relative to degrees on the dial, you&#8217;re going to make it warmer in the room.</p>
<p>I say previous is previous. It&#8217;s the past. Relative to where you are now, the previous things in life are those that are older. If I click a link that says &#8216;Previous Entries&#8217;, I expect those from the past &#8211; the older ones. &#8216;Next Entries&#8217; really isn&#8217;t particularly descriptive in my mind, but if it&#8217;s not a previous entry, what is it? Obviously in this case, if you put 2 and 2 together, next would mean newer.</p>
<p>Or we could just standardize the whole thing with &#8220;Older Entries&#8221; and &#8220;Newer Entries&#8221; and be done with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24878</link>
		<dc:creator>Seth</dc:creator>
		<pubDate>Fri, 09 Jun 2006 13:53:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24878</guid>
		<description>Standardized navigation links on blogs?  Next you&#039;ll want to get XHTML compliance, and some kinda insane syndication conformity. Sounds like crazy-talk to me.

I use &quot;previous entries&quot; to direct readers to entries I have written, uh, well, previously.  I do this because most of the time I&#039;m wearing a nifty policeman style hat that has &quot;Captain Obvious&quot; embroidered on the front.  That said, should there be a standard?  I think thats basically overthinking the concept of the navigation link and blogging in general.

It seems to me that the concept of fast-forward/rewind on a blog is generally already there.  The defaults on most blog systems are as we say and someone usually has to go out of their way to create the confusion mentioned... which possibly means they have a reason for having done so.</description>
		<content:encoded><![CDATA[<p>Standardized navigation links on blogs?  Next you&#8217;ll want to get XHTML compliance, and some kinda insane syndication conformity. Sounds like crazy-talk to me.</p>
<p>I use &#8220;previous entries&#8221; to direct readers to entries I have written, uh, well, previously.  I do this because most of the time I&#8217;m wearing a nifty policeman style hat that has &#8220;Captain Obvious&#8221; embroidered on the front.  That said, should there be a standard?  I think thats basically overthinking the concept of the navigation link and blogging in general.</p>
<p>It seems to me that the concept of fast-forward/rewind on a blog is generally already there.  The defaults on most blog systems are as we say and someone usually has to go out of their way to create the confusion mentioned&#8230; which possibly means they have a reason for having done so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: callistawolf</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24729</link>
		<dc:creator>callistawolf</dc:creator>
		<pubDate>Fri, 09 Jun 2006 00:53:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24729</guid>
		<description>Frankly?  I&#039;ve landed on page two of this blog and been completely confused by the page navigation.  hee..  I agree with Nick, that in my mind &quot;previous&quot; calls to mind something that happened in the past while &quot;next&quot; refers to more future events. :)</description>
		<content:encoded><![CDATA[<p>Frankly?  I&#8217;ve landed on page two of this blog and been completely confused by the page navigation.  hee..  I agree with Nick, that in my mind &#8220;previous&#8221; calls to mind something that happened in the past while &#8220;next&#8221; refers to more future events. <img src='http://www.bloggingpro.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EiNY</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24711</link>
		<dc:creator>EiNY</dc:creator>
		<pubDate>Thu, 08 Jun 2006 20:20:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24711</guid>
		<description>&lt;blockquote&gt;Should their be a standard in place? Which do you use, and why?&lt;/blockquote&gt;

Ahem, you mean &quot;Should THERE be a standard in place? Which do you use and why?

:)</description>
		<content:encoded><![CDATA[<blockquote><p>Should their be a standard in place? Which do you use, and why?</p></blockquote>
<p>Ahem, you mean &#8220;Should THERE be a standard in place? Which do you use and why?</p>
<p> <img src='http://www.bloggingpro.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24704</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Thu, 08 Jun 2006 16:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/06/07/1317/#comment-24704</guid>
		<description>I like to use previous/next in reference to date/time because this is what blogging really revolves around. My previous links go back in date/time from what you are looking at and next links go forward in date/time. I never quite understood the other way of doing it. The home page of a blog is in reality the &quot;end&quot; in terms of date/time so how can you click next and get something after the end?</description>
		<content:encoded><![CDATA[<p>I like to use previous/next in reference to date/time because this is what blogging really revolves around. My previous links go back in date/time from what you are looking at and next links go forward in date/time. I never quite understood the other way of doing it. The home page of a blog is in reality the &#8220;end&#8221; in terms of date/time so how can you click next and get something after the end?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

