<?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"
	>
<channel>
	<title>Comments on: Why UI? Why Not?</title>
	<atom:link href="http://www.attack-gecko.net/blog/2007/11/27/why-ui-why-not/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.attack-gecko.net/blog/2007/11/27/why-ui-why-not/</link>
	<description></description>
	<pubDate>Tue, 18 Nov 2008 09:49:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Gecko</title>
		<link>http://www.attack-gecko.net/blog/2007/11/27/why-ui-why-not/#comment-18527</link>
		<dc:creator>Gecko</dc:creator>
		<pubDate>Wed, 28 Nov 2007 18:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.attack-gecko.net/blog/2007/11/27/why-ui-why-not/#comment-18527</guid>
		<description>ant! you're alive!

setTimeout isn't cool for a couple reasons:
1) you can't pass arguments to your callback function which means i'd have to export my array and index to a global context
2) the timeout parameter is absolute time. so, say i call setTimeout multiple times with 1000, 2000, and 3000, so we have a function set to fire off once per second. now the user goes to a new tab and loads a page which hogs all resources for three seconds. when the user returns to your page, then it'll be clusterfuck of events firing off all at the same time. 

what i really want is a chain effect. after you do x, then do y and so on. it looks like the only way to do this in js is to blow up the function stack buy continually recursing.</description>
		<content:encoded><![CDATA[<p>ant! you&#8217;re alive!</p>
<p>setTimeout isn&#8217;t cool for a couple reasons:<br />
1) you can&#8217;t pass arguments to your callback function which means i&#8217;d have to export my array and index to a global context<br />
2) the timeout parameter is absolute time. so, say i call setTimeout multiple times with 1000, 2000, and 3000, so we have a function set to fire off once per second. now the user goes to a new tab and loads a page which hogs all resources for three seconds. when the user returns to your page, then it&#8217;ll be clusterfuck of events firing off all at the same time. </p>
<p>what i really want is a chain effect. after you do x, then do y and so on. it looks like the only way to do this in js is to blow up the function stack buy continually recursing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ant</title>
		<link>http://www.attack-gecko.net/blog/2007/11/27/why-ui-why-not/#comment-18510</link>
		<dc:creator>ant</dc:creator>
		<pubDate>Wed, 28 Nov 2007 13:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.attack-gecko.net/blog/2007/11/27/why-ui-why-not/#comment-18510</guid>
		<description>try this: setTimeout (http://www.w3schools.com/htmldom/met_win_settimeout.asp)! =)</description>
		<content:encoded><![CDATA[<p>try this: setTimeout (http://www.w3schools.com/htmldom/met_win_settimeout.asp)! =)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
