<?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: Using IFR at Sprint</title>
	<atom:link href="http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/</link>
	<description>Aaron Barker's random bablings</description>
	<lastBuildDate>Wed, 14 Nov 2007 22:52:28 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeff Croft</title>
		<link>http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/comment-page-1/#comment-25</link>
		<dc:creator>Jeff Croft</dc:creator>
		<pubDate>Thu, 16 Sep 2004 21:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/#comment-25</guid>
		<description>Great job! As you know, I&#039;ve been pimpin IFR, and particularly Mike Davidson&#039;s take on it -- sIFR on my site. The kind of information you&#039;ve given here is exactly what most people arne&#039;t &quot;getting&quot; about IFR. I think a lot of people are just saying, &quot;What&#039;s the big deal? Why is this better than using an image?&quot;

Those people are thinking about their personal site that has 10 headers total that are static and never change. When you start talking about CMSs, huge corporate sites, dynamic headers, and constant updates, you begin to realize why IFR makes so much sense.</description>
		<content:encoded><![CDATA[<p>Great job! As you know, I&#8217;ve been pimpin IFR, and particularly Mike Davidson&#8217;s take on it &#8212; sIFR on my site. The kind of information you&#8217;ve given here is exactly what most people arne&#8217;t &#8220;getting&#8221; about IFR. I think a lot of people are just saying, &#8220;What&#8217;s the big deal? Why is this better than using an image?&#8221;</p>
<p>Those people are thinking about their personal site that has 10 headers total that are static and never change. When you start talking about CMSs, huge corporate sites, dynamic headers, and constant updates, you begin to realize why IFR makes so much sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Schroeder</title>
		<link>http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/comment-page-1/#comment-17</link>
		<dc:creator>Sean Schroeder</dc:creator>
		<pubDate>Thu, 24 Jun 2004 14:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/#comment-17</guid>
		<description>Thanks for the breakdown! FIR is truly intriguing and an ongoing fascination for me. We&#039;ve been entertaining the idea of integrating the technique into the next build of our CMS would love to see a more detailed article discussing your approach, especially regardibg deviation from Shaun&#039;s approach. Great work! Thanks!</description>
		<content:encoded><![CDATA[<p>Thanks for the breakdown! FIR is truly intriguing and an ongoing fascination for me. We&#8217;ve been entertaining the idea of integrating the technique into the next build of our CMS would love to see a more detailed article discussing your approach, especially regardibg deviation from Shaun&#8217;s approach. Great work! Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/comment-page-1/#comment-16</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Thu, 24 Jun 2004 03:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/#comment-16</guid>
		<description>I really liked seeing the cost analysis here, something that us designers dont always take into consideration... thanks for the write up! :)</description>
		<content:encoded><![CDATA[<p>I really liked seeing the cost analysis here, something that us designers dont always take into consideration&#8230; thanks for the write up! <img src='http://www.zelph.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Moritz</title>
		<link>http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/comment-page-1/#comment-11</link>
		<dc:creator>Chris Moritz</dc:creator>
		<pubDate>Mon, 21 Jun 2004 15:38:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/#comment-11</guid>
		<description>Hear hear!  I smell an A List Apart article a-brewin&#039;.</description>
		<content:encoded><![CDATA[<p>Hear hear!  I smell an A List Apart article a-brewin&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Point Break &#124; Waves</title>
		<link>http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/comment-page-1/#comment-10</link>
		<dc:creator>Point Break &#124; Waves</dc:creator>
		<pubDate>Mon, 21 Jun 2004 04:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.zelph.com/archives/2004/06/20/using-ifr-at-sprint/#comment-10</guid>
		<description>&lt;strong&gt;www.sprint.com/business - a CSS mega-relaunch&lt;/strong&gt;
More Sprint&#160;CSS&#160;Goodness&#8482; - featuring Inman Flash Replacement.

First came the sprintpcs.com redesign, then the sprint.com homepage, then some here, there, everywhere. And now, introducing Sprint Business, housing all business-oriente...</description>
		<content:encoded><![CDATA[<p><strong><a href="http://www.sprint.com/business" rel="nofollow">http://www.sprint.com/business</a> &#8211; a CSS mega-relaunch</strong><br />
More Sprint&nbsp;CSS&nbsp;Goodness&trade; &#8211; featuring Inman Flash Replacement.</p>
<p>First came the sprintpcs.com redesign, then the sprint.com homepage, then some here, there, everywhere. And now, introducing Sprint Business, housing all business-oriente&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
