<?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: NSFlow: A Call to Apple For CoverFlow System-Wide</title>
	<atom:link href="http://dbachrach.com/blog/2007/08/nsflow-a-call-to-apple-for-coverflow-system-wide/feed/" rel="self" type="application/rss+xml" />
	<link>http://dbachrach.com/blog/2007/08/nsflow-a-call-to-apple-for-coverflow-system-wide/</link>
	<description>a developer blog</description>
	<lastBuildDate>Fri, 03 Sep 2010 13:40:21 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jake</title>
		<link>http://dbachrach.com/blog/2007/08/nsflow-a-call-to-apple-for-coverflow-system-wide/#comment-772</link>
		<dc:creator>Jake</dc:creator>
		<pubDate>Wed, 23 Apr 2008 10:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://dbachrach.com/blog/2007/08/15/nsflow-a-call-to-apple-for-coverflow-system-wide/#comment-772</guid>
		<description>CoverFlow API is here - its just private.  Try a gander at the private parts of ImageKit using class-dump</description>
		<content:encoded><![CDATA[<p>CoverFlow API is here &#8211; its just private.  Try a gander at the private parts of ImageKit using class-dump</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt L.</title>
		<link>http://dbachrach.com/blog/2007/08/nsflow-a-call-to-apple-for-coverflow-system-wide/#comment-771</link>
		<dc:creator>Matt L.</dc:creator>
		<pubDate>Mon, 01 Oct 2007 07:51:20 +0000</pubDate>
		<guid isPermaLink="false">http://dbachrach.com/blog/2007/08/15/nsflow-a-call-to-apple-for-coverflow-system-wide/#comment-771</guid>
		<description>I agree with you that Apple *should* create an API for it. But I dont want an API for it. The last thing I want to see is CoverFlow being incorporated into applications where it doesn&#039;t make sense. Unfortunately this would be more often than where it does make sense. Apple doesn&#039;t create superfluous eye candy. They create/implement functional eye candy. CoverFlow is cool tech. The last thing Apple wants is for it to get over saturated. When Form is more important than function you wind up with apps like Disco. :)</description>
		<content:encoded><![CDATA[<p>I agree with you that Apple *should* create an API for it. But I dont want an API for it. The last thing I want to see is CoverFlow being incorporated into applications where it doesn&#8217;t make sense. Unfortunately this would be more often than where it does make sense. Apple doesn&#8217;t create superfluous eye candy. They create/implement functional eye candy. CoverFlow is cool tech. The last thing Apple wants is for it to get over saturated. When Form is more important than function you wind up with apps like Disco. <img src='http://dbachrach.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

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