<?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: Post Show &amp; Updates</title>
	<atom:link href="http://www.midnightcheese.com/2007/01/post-show-updates/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.midnightcheese.com/2007/01/post-show-updates/</link>
	<description>Art, Design, and Technology</description>
	<lastBuildDate>Tue, 27 Jul 2010 05:45:12 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jim.</title>
		<link>http://www.midnightcheese.com/2007/01/post-show-updates/comment-page-1/#comment-224665</link>
		<dc:creator>Jim.</dc:creator>
		<pubDate>Thu, 01 Feb 2007 21:51:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.midnightcheese.com/index.php?p=443#comment-224665</guid>
		<description>My amateur advice, is to start by picking a random rowid in the newest 10-15% of your repository. Then move at n+1 from there. At that point, you can do a forward and backward button relatively painlessly up to the point that the end of the repository is reached. 

If you want to mix it up more, you can pick a random number, have it move forward x number of times, then pick randomly again. It would be a little more complicated to do the history, but still more manageable that total randomness.

Are you going to do total history, or say the last 10? If you limit the browsable history, then you can easily have a small text file (or even private array) that keeps up with rowids as you go. Thus achieving randomness and history, just be sure the keep the array in bounds so you don&#039;t eat memory.

I probably didn&#039;t say anything that you two haven&#039;t already thought out. I think the bounded array to hold history would be the coolest. You&#039;d have to do Filesystem I/O if you want to save the history elsewhere for preservation, which would be a performance hit.</description>
		<content:encoded><![CDATA[<p>My amateur advice, is to start by picking a random rowid in the newest 10-15% of your repository. Then move at n+1 from there. At that point, you can do a forward and backward button relatively painlessly up to the point that the end of the repository is reached. </p>
<p>If you want to mix it up more, you can pick a random number, have it move forward x number of times, then pick randomly again. It would be a little more complicated to do the history, but still more manageable that total randomness.</p>
<p>Are you going to do total history, or say the last 10? If you limit the browsable history, then you can easily have a small text file (or even private array) that keeps up with rowids as you go. Thus achieving randomness and history, just be sure the keep the array in bounds so you don&#8217;t eat memory.</p>
<p>I probably didn&#8217;t say anything that you two haven&#8217;t already thought out. I think the bounded array to hold history would be the coolest. You&#8217;d have to do Filesystem I/O if you want to save the history elsewhere for preservation, which would be a performance hit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cale</title>
		<link>http://www.midnightcheese.com/2007/01/post-show-updates/comment-page-1/#comment-224637</link>
		<dc:creator>Cale</dc:creator>
		<pubDate>Thu, 01 Feb 2007 15:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.midnightcheese.com/index.php?p=443#comment-224637</guid>
		<description>The widget randomly pulls from the database when a request is made. We haven&#039;t really talked about how we&#039;re going to order the web gallery. At the moment I think we have it set to display sorted by row ID. I figure we should probably do that, starting with the newest first just to keep the content fresh whenever you navigate to the page. Any ideas are welcome, however.</description>
		<content:encoded><![CDATA[<p>The widget randomly pulls from the database when a request is made. We haven&#8217;t really talked about how we&#8217;re going to order the web gallery. At the moment I think we have it set to display sorted by row ID. I figure we should probably do that, starting with the newest first just to keep the content fresh whenever you navigate to the page. Any ideas are welcome, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim.</title>
		<link>http://www.midnightcheese.com/2007/01/post-show-updates/comment-page-1/#comment-224620</link>
		<dc:creator>Jim.</dc:creator>
		<pubDate>Thu, 01 Feb 2007 14:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.midnightcheese.com/index.php?p=443#comment-224620</guid>
		<description>I&#039;ve asked you this before, but does Candor cycle randomly, or is it in a set order? I&#039;m just wondering if you are going to have a local repository of sorts to keep up with history, or if you are just going to randomly start people on a certain part of the cycle, and use n-1 to go back.

I don&#039;t even know if that makes sense.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve asked you this before, but does Candor cycle randomly, or is it in a set order? I&#8217;m just wondering if you are going to have a local repository of sorts to keep up with history, or if you are just going to randomly start people on a certain part of the cycle, and use n-1 to go back.</p>
<p>I don&#8217;t even know if that makes sense.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
