<?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: JavaScript slideshow fun</title>
	<atom:link href="http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/feed/" rel="self" type="application/rss+xml" />
	<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/</link>
	<description>Adventures creations and musings from a girl geek</description>
	<pubDate>Wed, 20 Aug 2008 08:28:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: otro blog más &#187; Unos cuantos de desarrollo web (LXXXIV)</title>
		<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/#comment-11</link>
		<dc:creator>otro blog más &#187; Unos cuantos de desarrollo web (LXXXIV)</dc:creator>
		<pubDate>Sun, 09 Apr 2006 19:40:17 +0000</pubDate>
		<guid isPermaLink="false">http://notes.natbat.net/?p=16#comment-11</guid>
		<description>[...] Cosillas de JavaScript, DHTML, DOMScripting o cómo se le quiera llamar&#8230; Un fundido de imágenes, otro y un tercero. DOMTab son unas pestañas bastante apañadas, justo igual que JavaScript Tabifier. [...]</description>
		<content:encoded><![CDATA[<p>[...] Cosillas de JavaScript, DHTML, DOMScripting o cómo se le quiera llamar&#8230; Un fundido de imágenes, otro y un tercero. DOMTab son unas pestañas bastante apañadas, justo igual que JavaScript Tabifier. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dustin Diaz</title>
		<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/#comment-10</link>
		<dc:creator>Dustin Diaz</dc:creator>
		<pubDate>Tue, 21 Mar 2006 06:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://notes.natbat.net/?p=16#comment-10</guid>
		<description>Nat, just jumped here from Simon's site ;) - if you're looking to get fancy with listeners, definitely check out the Y! util.Event stuff.

Stuart, the hang Glider was much cooler. at least you don't have a funny pop-up-clown-box like Cameron's book. Some of these covers just trip me out - you really have to question what they were thinking.</description>
		<content:encoded><![CDATA[<p>Nat, just jumped here from Simon&#8217;s site ;) - if you&#8217;re looking to get fancy with listeners, definitely check out the Y! util.Event stuff.</p>
<p>Stuart, the hang Glider was much cooler. at least you don&#8217;t have a funny pop-up-clown-box like Cameron&#8217;s book. Some of these covers just trip me out - you really have to question what they were thinking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sil</title>
		<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/#comment-9</link>
		<dc:creator>sil</dc:creator>
		<pubDate>Sat, 25 Feb 2006 03:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://notes.natbat.net/?p=16#comment-9</guid>
		<description>Frog cover...your guess is as good as mine. The covers happen somewhere I don't know about. :)</description>
		<content:encoded><![CDATA[<p>Frog cover&#8230;your guess is as good as mine. The covers happen somewhere I don&#8217;t know about. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: natbat</title>
		<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/#comment-8</link>
		<dc:creator>natbat</dc:creator>
		<pubDate>Thu, 23 Feb 2006 16:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://notes.natbat.net/?p=16#comment-8</guid>
		<description>I did look at using &lt;a href="http://dean.edwards.name/weblog/2005/09/busted/" rel="nofollow"&gt; DOMContentLoaded and Deanâ€™s defer trick&lt;/a&gt; but the &lt;a href="http://natbat.wordpress.com/2006/02/23/fixing-a-few-javascript-slideshow-loose-ends/" rel="nofollow"&gt;solution&lt;/a&gt; I came up with worked so the slideshow no-longer hangs while the images load, I will probably go back and use that trick anyway though, I just wanted to see if the try / catch on the DOM loading worked as a quick fix for the time being. Thanks for the suggestion ... and the book! and I much prefer the frog cover :)</description>
		<content:encoded><![CDATA[<p>I did look at using <a href="http://dean.edwards.name/weblog/2005/09/busted/" rel="nofollow"> DOMContentLoaded and Deanâ€™s defer trick</a> but the <a href="http://natbat.wordpress.com/2006/02/23/fixing-a-few-javascript-slideshow-loose-ends/" rel="nofollow">solution</a> I came up with worked so the slideshow no-longer hangs while the images load, I will probably go back and use that trick anyway though, I just wanted to see if the try / catch on the DOM loading worked as a quick fix for the time being. Thanks for the suggestion &#8230; and the book! and I much prefer the frog cover :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Dunck</title>
		<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/#comment-7</link>
		<dc:creator>Jeremy Dunck</dc:creator>
		<pubDate>Thu, 23 Feb 2006 10:30:29 +0000</pubDate>
		<guid isPermaLink="false">http://notes.natbat.net/?p=16#comment-7</guid>
		<description>Hey Stuart-- what's with the frog cover?  The one's I've bought (2) both have the hang glider...</description>
		<content:encoded><![CDATA[<p>Hey Stuart&#8211; what&#8217;s with the frog cover?  The one&#8217;s I&#8217;ve bought (2) both have the hang glider&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Natalie Downe &#187; Fixing a few JavaScript slideshow loose ends</title>
		<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/#comment-6</link>
		<dc:creator>Natalie Downe &#187; Fixing a few JavaScript slideshow loose ends</dc:creator>
		<pubDate>Thu, 23 Feb 2006 09:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://notes.natbat.net/?p=16#comment-6</guid>
		<description>[...] As pointed out by Jeremy, my linkable slideshow needed some work to fix the load order of the page without altering the &#8216;unobtrusiveness&#8217; of its behaviour. [...]</description>
		<content:encoded><![CDATA[<p>[...] As pointed out by Jeremy, my linkable slideshow needed some work to fix the load order of the page without altering the &#8216;unobtrusiveness&#8217; of its behaviour. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sil</title>
		<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/#comment-5</link>
		<dc:creator>sil</dc:creator>
		<pubDate>Thu, 23 Feb 2006 08:33:04 +0000</pubDate>
		<guid isPermaLink="false">http://notes.natbat.net/?p=16#comment-5</guid>
		<description>Nice. I like that. As an alternative to Jeremy's suggestions, you might want to hook DOMContentLoaded (in Firefox) and use Dean's defer trick (http://dean.edwards.name/weblog/2005/09/busted/) in IE so you don't hang while the images are loading. 

And thanks for the book pimpage, although you of course know that the technical editor did all the *hard* work. :-)</description>
		<content:encoded><![CDATA[<p>Nice. I like that. As an alternative to Jeremy&#8217;s suggestions, you might want to hook DOMContentLoaded (in Firefox) and use Dean&#8217;s defer trick (http://dean.edwards.name/weblog/2005/09/busted/) in IE so you don&#8217;t hang while the images are loading. </p>
<p>And thanks for the book pimpage, although you of course know that the technical editor did all the *hard* work. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: natbat</title>
		<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/#comment-4</link>
		<dc:creator>natbat</dc:creator>
		<pubDate>Wed, 22 Feb 2006 23:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://notes.natbat.net/?p=16#comment-4</guid>
		<description>Thanks Jeremy that's really useful. The second method, like you said, does sound a cleaner way of approaching the solution - Ill have a go at that :)</description>
		<content:encoded><![CDATA[<p>Thanks Jeremy that&#8217;s really useful. The second method, like you said, does sound a cleaner way of approaching the solution - Ill have a go at that :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Dunck</title>
		<link>http://notes.natbat.net/2006/02/22/javascript-slideshow-fun/#comment-3</link>
		<dc:creator>Jeremy Dunck</dc:creator>
		<pubDate>Wed, 22 Feb 2006 22:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://notes.natbat.net/?p=16#comment-3</guid>
		<description>Also consider putting a prev/next link set at the top, where it's fixed location will make it easier to repeatedly click the same link without re-mousing.

... And the long load time before reorging the page into the slideshow onload may be confusing.  I can imagine people thinking its a regular list of photos, scrolling down (as it continues to load) and then being surprised when the page pops down to the first image.

Two ways I can think of to address that:  

1) Don't wait for onload to start scripting: you could immediately start watching for img elms (even as the doc is being loaded) and hide them as they are parsed into the DOM.

2) From script, immediately style all images to be hidden, then onload fix up your viewer and un-hide them.

... I think the 2nd way is better.  In the 1st way, you're likely to be fighting rendering reflows with the first approach.

(Sorry for the criticism-- I do like the general result. :))</description>
		<content:encoded><![CDATA[<p>Also consider putting a prev/next link set at the top, where it&#8217;s fixed location will make it easier to repeatedly click the same link without re-mousing.</p>
<p>&#8230; And the long load time before reorging the page into the slideshow onload may be confusing.  I can imagine people thinking its a regular list of photos, scrolling down (as it continues to load) and then being surprised when the page pops down to the first image.</p>
<p>Two ways I can think of to address that:  </p>
<p>1) Don&#8217;t wait for onload to start scripting: you could immediately start watching for img elms (even as the doc is being loaded) and hide them as they are parsed into the DOM.</p>
<p>2) From script, immediately style all images to be hidden, then onload fix up your viewer and un-hide them.</p>
<p>&#8230; I think the 2nd way is better.  In the 1st way, you&#8217;re likely to be fighting rendering reflows with the first approach.</p>
<p>(Sorry for the criticism&#8211; I do like the general result. :))</p>
]]></content:encoded>
	</item>
</channel>
</rss>
