<?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: Dead-simple pagination wizardry with TurboGears 2</title>
	<atom:link href="http://blog.curiasolutions.com/2009/11/dead-simple-pagination-wizardry-with-turbogears-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.curiasolutions.com/2009/11/dead-simple-pagination-wizardry-with-turbogears-2/</link>
	<description>Technology thoughts and ideas</description>
	<lastBuildDate>Tue, 13 Jul 2010 02:50:28 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Seth</title>
		<link>http://blog.curiasolutions.com/2009/11/dead-simple-pagination-wizardry-with-turbogears-2/comment-page-1/#comment-48</link>
		<dc:creator>Seth</dc:creator>
		<pubDate>Sat, 21 Nov 2009 23:07:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.curiasolutions.com/?p=556#comment-48</guid>
		<description>Lukas- Excellent. Thanks for your contribution!</description>
		<content:encoded><![CDATA[<p>Lukas- Excellent. Thanks for your contribution!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lukasg</title>
		<link>http://blog.curiasolutions.com/2009/11/dead-simple-pagination-wizardry-with-turbogears-2/comment-page-1/#comment-46</link>
		<dc:creator>lukasg</dc:creator>
		<pubDate>Thu, 19 Nov 2009 20:28:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.curiasolutions.com/?p=556#comment-46</guid>
		<description>very useful article, thank you seth!

I merged some of your info into what I think could be a next version of the tutorial: http://rapidprototype.ch/tg/docs/pagination-ajax/main/Pagination/index.html</description>
		<content:encoded><![CDATA[<p>very useful article, thank you seth!</p>
<p>I merged some of your info into what I think could be a next version of the tutorial: <a href="http://rapidprototype.ch/tg/docs/pagination-ajax/main/Pagination/index.html" rel="nofollow">http://rapidprototype.ch/tg/docs/pagination-ajax/main/Pagination/index.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth</title>
		<link>http://blog.curiasolutions.com/2009/11/dead-simple-pagination-wizardry-with-turbogears-2/comment-page-1/#comment-45</link>
		<dc:creator>Seth</dc:creator>
		<pubDate>Sun, 08 Nov 2009 19:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.curiasolutions.com/?p=556#comment-45</guid>
		<description>bloodearnest,

You could definitely go that route, but as I said I was being intentionally verbose in order to be clear about the possible &quot;issues&quot; with the out-of-the-box pagination.

Thanks for your input.</description>
		<content:encoded><![CDATA[<p>bloodearnest,</p>
<p>You could definitely go that route, but as I said I was being intentionally verbose in order to be clear about the possible &#8220;issues&#8221; with the out-of-the-box pagination.</p>
<p>Thanks for your input.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bloodearnest</title>
		<link>http://blog.curiasolutions.com/2009/11/dead-simple-pagination-wizardry-with-turbogears-2/comment-page-1/#comment-44</link>
		<dc:creator>bloodearnest</dc:creator>
		<pubDate>Fri, 06 Nov 2009 11:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.curiasolutions.com/?p=556#comment-44</guid>
		<description>I may be missing something, but why not include all the limit/offset boilerplate in a new paginate decorator. This could strip of the incoming &quot;page&quot; variable from POST/GET vars, and it&#039;s all invisible to the function.
You could ecven use the original paginate decorator to do the actual filtering like in the above example...</description>
		<content:encoded><![CDATA[<p>I may be missing something, but why not include all the limit/offset boilerplate in a new paginate decorator. This could strip of the incoming &#8220;page&#8221; variable from POST/GET vars, and it&#8217;s all invisible to the function.<br />
You could ecven use the original paginate decorator to do the actual filtering like in the above example&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
