<?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: Project: CNN Image Gallery</title>
	<atom:link href="http://www.kennybunch.com/blog/2007/07/project-cnn-image-gallery/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kennybunch.com/blog/2007/07/project-cnn-image-gallery/</link>
	<description></description>
	<lastBuildDate>Tue, 25 Mar 2008 13:45:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Kenny Bunch</title>
		<link>http://www.kennybunch.com/blog/2007/07/project-cnn-image-gallery/comment-page-1/#comment-147</link>
		<dc:creator>Kenny Bunch</dc:creator>
		<pubDate>Wed, 11 Jul 2007 13:54:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.kennybunch.com/blog/?p=58#comment-147</guid>
		<description>PJ,
I think it&#039;s based on a few things. First, Flash is a lot quicker to develop and get the look and feel right. Also, you have the notion that a Flash asset is a single instance. It makes it completely portable. For instance, if you want to snap that into a viral widget, it&#039;s already ready and will work everywhere (a lot of sites disable js code). The code is also lot more manageable and debugable too.  Some of the js engines are getting better at catching issues, but due to the complete dynamic nature of the language it&#039;s harder to find bugs up front. Could the gallery be done in DHTML? Certainly. You can do a lot more complex apps than that with DHTML. So this one could have been an either or situation, but it was just simpler in Flash

I agree with you on using DHTML when needed. I was a DHTML wizard before doing Flash and still use it when it&#039;s the better solution. If you look at the rest of CNN, you will notice a LOT of DHTML going on. In these places it makes more sense. The functionality screams for it and would be a bad choice for Flash. It&#039;s about picking the right technology for the job.</description>
		<content:encoded><![CDATA[<p>PJ,<br />
I think it&#8217;s based on a few things. First, Flash is a lot quicker to develop and get the look and feel right. Also, you have the notion that a Flash asset is a single instance. It makes it completely portable. For instance, if you want to snap that into a viral widget, it&#8217;s already ready and will work everywhere (a lot of sites disable js code). The code is also lot more manageable and debugable too.  Some of the js engines are getting better at catching issues, but due to the complete dynamic nature of the language it&#8217;s harder to find bugs up front. Could the gallery be done in DHTML? Certainly. You can do a lot more complex apps than that with DHTML. So this one could have been an either or situation, but it was just simpler in Flash</p>
<p>I agree with you on using DHTML when needed. I was a DHTML wizard before doing Flash and still use it when it&#8217;s the better solution. If you look at the rest of CNN, you will notice a LOT of DHTML going on. In these places it makes more sense. The functionality screams for it and would be a bad choice for Flash. It&#8217;s about picking the right technology for the job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: P.J. Onori</title>
		<link>http://www.kennybunch.com/blog/2007/07/project-cnn-image-gallery/comment-page-1/#comment-146</link>
		<dc:creator>P.J. Onori</dc:creator>
		<pubDate>Wed, 11 Jul 2007 05:25:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.kennybunch.com/blog/?p=58#comment-146</guid>
		<description>It is indeed very nice work - my only question is why their decision for Flash. As someone who develops Flash applications, I definitely understand the appeal and benefits of Flash/Flex, but I am beginning to think that the basic slideshow paradigm, is more suited for implementation in advanced Javascript. There are definitely times where Flash would be the better solution (i.e. high motion, rich interaction models, etc.) but for 90% of slideshows out there, Javascript can take care of it.

This is by no means a knock on your work - it&#039;s great. Rather, it&#039;s a question on why you think the client decided to go the Flash route? Any thoughts on that?</description>
		<content:encoded><![CDATA[<p>It is indeed very nice work &#8211; my only question is why their decision for Flash. As someone who develops Flash applications, I definitely understand the appeal and benefits of Flash/Flex, but I am beginning to think that the basic slideshow paradigm, is more suited for implementation in advanced Javascript. There are definitely times where Flash would be the better solution (i.e. high motion, rich interaction models, etc.) but for 90% of slideshows out there, Javascript can take care of it.</p>
<p>This is by no means a knock on your work &#8211; it&#8217;s great. Rather, it&#8217;s a question on why you think the client decided to go the Flash route? Any thoughts on that?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.283 seconds -->

