<?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: Endless pages</title>
	<atom:link href="http://coldconstructs.com/2008/06/endlesspages/feed/" rel="self" type="application/rss+xml" />
	<link>http://coldconstructs.com/2008/06/endlesspages/</link>
	<description>Creations of Corey Birnbaum</description>
	<lastBuildDate>Wed, 18 Jan 2012 21:34:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Corey</title>
		<link>http://coldconstructs.com/2008/06/endlesspages/#comment-5</link>
		<dc:creator>Corey</dc:creator>
		<pubDate>Mon, 21 Jul 2008 00:23:13 +0000</pubDate>
		<guid isPermaLink="false">http://coldconstructs.com/?p=28#comment-5</guid>
		<description>You can still have a footer if you use a div with &quot;display:block; position:fixed; bottom:0;&quot; which is how I hover my current menu bar up top there (only with top:0 obviously).

I understand the mousewheel issues but they&#039;ll eventually get worked out as standards continue mature and browsers continue to adopt them. It&#039;s not very good at the moment though, I agree.

I don&#039;t exactly see the progress issue though. The point is to provide users with an uninterrupted stream of content. Each page/chunk is still marked of course, just as I did in my demo, so there is no navigational confusion. But there isn&#039;t supposed to be an end -- just an end to the user&#039;s interest, at which point they simply leave. 

If it really matters to you though, you can still determine the number of chunks currently in the database and display that between each chunk (eg &quot;page 1 of 30&quot;).</description>
		<content:encoded><![CDATA[<p>You can still have a footer if you use a div with &#8220;display:block; position:fixed; bottom:0;&#8221; which is how I hover my current menu bar up top there (only with top:0 obviously).</p>
<p>I understand the mousewheel issues but they&#8217;ll eventually get worked out as standards continue mature and browsers continue to adopt them. It&#8217;s not very good at the moment though, I agree.</p>
<p>I don&#8217;t exactly see the progress issue though. The point is to provide users with an uninterrupted stream of content. Each page/chunk is still marked of course, just as I did in my demo, so there is no navigational confusion. But there isn&#8217;t supposed to be an end &#8212; just an end to the user&#8217;s interest, at which point they simply leave. </p>
<p>If it really matters to you though, you can still determine the number of chunks currently in the database and display that between each chunk (eg &#8220;page 1 of 30&#8243;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: m3mnoch</title>
		<link>http://coldconstructs.com/2008/06/endlesspages/#comment-4</link>
		<dc:creator>m3mnoch</dc:creator>
		<pubDate>Wed, 16 Jul 2008 15:52:36 +0000</pubDate>
		<guid isPermaLink="false">http://coldconstructs.com/?p=28#comment-4</guid>
		<description>btw, where the endless scrolling breaks is if you have a footer.  that means you have to have a &quot;frame&quot; scrollbar thing.  or an javascript-floaty footer.  that has all kinds of implications from mousewheel support to users getting frustrated because they never succeed at finding the &quot;end&quot; of the content and thus can&#039;t guage their progress to more specialized external api consuming issues.  aka pages are no longer pages.

don&#039;t get me wrong, i think it&#039;s neat.  but, even tho ext has been doing it for years now, there&#039;s a reason it hasn&#039;t seen wide adoption.  there are a few specialized places where it&#039;s handy.  paging search results just is not one of them.

m3mnoch.</description>
		<content:encoded><![CDATA[<p>btw, where the endless scrolling breaks is if you have a footer.  that means you have to have a &#8220;frame&#8221; scrollbar thing.  or an javascript-floaty footer.  that has all kinds of implications from mousewheel support to users getting frustrated because they never succeed at finding the &#8220;end&#8221; of the content and thus can&#8217;t guage their progress to more specialized external api consuming issues.  aka pages are no longer pages.</p>
<p>don&#8217;t get me wrong, i think it&#8217;s neat.  but, even tho ext has been doing it for years now, there&#8217;s a reason it hasn&#8217;t seen wide adoption.  there are a few specialized places where it&#8217;s handy.  paging search results just is not one of them.</p>
<p>m3mnoch.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

