<?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: Building a Pagination System with AJAX</title>
	<atom:link href="http://ajaxian.com/archives/building-a-pagination-system-with-ajax/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Sun, 21 Mar 2010 02:12:15 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-247465</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 22 Feb 2007 15:26:53 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-247465</guid>
		<description>There is a place for this. Though native scrollbars are preferred, there is the issue of them being rendered above ANY z-index. If you have a grid in the center of the page and you create DHTML tooltips or something like that the scrollbar will always be on top and will interfere with any DHTML you try to layer above it. In this case &quot;artificial&quot; scrollbars are a great solution as you can control which layer they render on.</description>
		<content:encoded><![CDATA[<p>There is a place for this. Though native scrollbars are preferred, there is the issue of them being rendered above ANY z-index. If you have a grid in the center of the page and you create DHTML tooltips or something like that the scrollbar will always be on top and will interfere with any DHTML you try to layer above it. In this case &#8220;artificial&#8221; scrollbars are a great solution as you can control which layer they render on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ePeaksoft</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-172446</link>
		<dc:creator>ePeaksoft</dc:creator>
		<pubDate>Thu, 09 Nov 2006 15:51:45 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-172446</guid>
		<description>&lt;a href=&quot;www.epeaksoft.com&quot; rel=&quot;nofollow&quot;&gt;software outsourcing in China&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p><a href="www.epeaksoft.com" rel="nofollow">software outsourcing in China</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-76408</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Sun, 27 Aug 2006 22:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-76408</guid>
		<description>Alex,

I&#039;ve been using your stuff since 2002 (netwindows) and looking forward to checking out dojo.  Just want to point out that a virtual scrollbar has distinct advantages for large datasets.
Large amounts of data can be stored in memory on the client as an xmldomdocument.  Rendering large amounts of data as dhtml is very costly especially as the user can only see a small subset of the data at any given moment.  Think of the &quot;ajax&quot; screen as a virtual window on the dataset that can be sorted or filtered dynamically then displayed in the virtual window with eyeblink speed without altering the underlying data.  This arrangement would benefit greatly from a virtual scrollbar.

Charlie</description>
		<content:encoded><![CDATA[<p>Alex,</p>
<p>I&#8217;ve been using your stuff since 2002 (netwindows) and looking forward to checking out dojo.  Just want to point out that a virtual scrollbar has distinct advantages for large datasets.<br />
Large amounts of data can be stored in memory on the client as an xmldomdocument.  Rendering large amounts of data as dhtml is very costly especially as the user can only see a small subset of the data at any given moment.  Think of the &#8220;ajax&#8221; screen as a virtual window on the dataset that can be sorted or filtered dynamically then displayed in the virtual window with eyeblink speed without altering the underlying data.  This arrangement would benefit greatly from a virtual scrollbar.</p>
<p>Charlie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-76387</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Sun, 27 Aug 2006 22:11:25 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-76387</guid>
		<description>Sorry but using pages for grid data is simply a hack, an aberration necessitated by the pre-ajax scalability issues of web applications.  What reasonalbe  non-web application has ever used the concept of pages to display grid data?  
The fact that an ajax application is going to the web and dynamically pulling data or pulling from an in-memory datacache should be completely transparent to the user, the purpose when using this technology with ajax is to minimize roundtrips.  Search, sort and filter should similarly work in a manner that works transparently from the users perspective.  The goal is to produce a rich-client experience on the web that mimics in all aspects traditional client server and scales to the web.</description>
		<content:encoded><![CDATA[<p>Sorry but using pages for grid data is simply a hack, an aberration necessitated by the pre-ajax scalability issues of web applications.  What reasonalbe  non-web application has ever used the concept of pages to display grid data?<br />
The fact that an ajax application is going to the web and dynamically pulling data or pulling from an in-memory datacache should be completely transparent to the user, the purpose when using this technology with ajax is to minimize roundtrips.  Search, sort and filter should similarly work in a manner that works transparently from the users perspective.  The goal is to produce a rich-client experience on the web that mimics in all aspects traditional client server and scales to the web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-21290</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 07 Jun 2006 19:59:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-21290</guid>
		<description>Beyond the scroll bars ...
I am not a fan of scrolling pagination period. In some cases its fine, but there has to be an available option to quickly navigate to page X. If I find an item at position 1240 in the search results, leave the search page and come back, I don&#039;t want to scroll all the way to it when I know it was on page 12. That why I hate the M$ Live demo. A simple dropdown to fetch the appropriate page via AJAX is all that&#039;s needed.</description>
		<content:encoded><![CDATA[<p>Beyond the scroll bars &#8230;<br />
I am not a fan of scrolling pagination period. In some cases its fine, but there has to be an available option to quickly navigate to page X. If I find an item at position 1240 in the search results, leave the search page and come back, I don&#8217;t want to scroll all the way to it when I know it was on page 12. That why I hate the M$ Live demo. A simple dropdown to fetch the appropriate page via AJAX is all that&#8217;s needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marty</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-20490</link>
		<dc:creator>Marty</dc:creator>
		<pubDate>Tue, 06 Jun 2006 13:57:59 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-20490</guid>
		<description>A nice idea, but no, fake scrollbars are simply not going to cut it.  NEXT!</description>
		<content:encoded><![CDATA[<p>A nice idea, but no, fake scrollbars are simply not going to cut it.  NEXT!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ros</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-20347</link>
		<dc:creator>Ros</dc:creator>
		<pubDate>Tue, 06 Jun 2006 09:32:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-20347</guid>
		<description>At &lt;a&gt;openRico.org&lt;/a&gt; we&#039;ve had a live grid using a scrollbar to replace pagination using Ajax for about a year, whats more ours manages data caching and buffering preventing any problems with network latency..

A guide on how to use it unobtrusively and replace pagniation links will be published shortly, so you can have accesible and resposive data presentation...</description>
		<content:encoded><![CDATA[<p>At <a>openRico.org</a> we&#8217;ve had a live grid using a scrollbar to replace pagination using Ajax for about a year, whats more ours manages data caching and buffering preventing any problems with network latency..</p>
<p>A guide on how to use it unobtrusively and replace pagniation links will be published shortly, so you can have accesible and resposive data presentation&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Russell</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-20313</link>
		<dc:creator>Alex Russell</dc:creator>
		<pubDate>Tue, 06 Jun 2006 08:04:37 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-20313</guid>
		<description>I&#039;m sorry, but non-native scrollbars are surely a signpost that you&#039;re hurtling down the road to hell with reckless abandon. You can just make an absolutely positioned element inside of a overflow: auto; element and get the same effect without breaking all kinds of native behaviors that users rely on.

Oof.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry, but non-native scrollbars are surely a signpost that you&#8217;re hurtling down the road to hell with reckless abandon. You can just make an absolutely positioned element inside of a overflow: auto; element and get the same effect without breaking all kinds of native behaviors that users rely on.</p>
<p>Oof.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: En vrac #4 at Gate Nine</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-20272</link>
		<dc:creator>En vrac #4 at Gate Nine</dc:creator>
		<pubDate>Tue, 06 Jun 2006 06:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-20272</guid>
		<description>[...] Comment construire un systÃ¨me de pagination en Ajax : Ajaxian.com [...]</description>
		<content:encoded><![CDATA[<p>[...] Comment construire un systÃ¨me de pagination en Ajax : Ajaxian.com [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Similson</title>
		<link>http://ajaxian.com/archives/building-a-pagination-system-with-ajax/comment-page-1#comment-20130</link>
		<dc:creator>John Similson</dc:creator>
		<pubDate>Mon, 05 Jun 2006 22:18:53 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/building-a-pagination-system-with-ajax#comment-20130</guid>
		<description>These guys: www.mpire.com 

Do a really good job of this in their listing tool. I&#039;ve tried picking apart their code but it&#039;s kinda complicated.</description>
		<content:encoded><![CDATA[<p>These guys: <a href="http://www.mpire.com" rel="nofollow">http://www.mpire.com</a> </p>
<p>Do a really good job of this in their listing tool. I&#8217;ve tried picking apart their code but it&#8217;s kinda complicated.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
