<?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: New media guidelines for old design problems</title>
	<atom:link href="http://www.brunobergher.com/blog/2007/10/09/new-media-guidelines-for-old-design-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brunobergher.com/blog/2007/10/09/new-media-guidelines-for-old-design-problems/</link>
	<description></description>
	<lastBuildDate>Sun, 19 Apr 2009 18:18:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: brunobergher::blog · Past Thoughts &#187; OK, we do 3D&#8230; But how do we design for it?</title>
		<link>http://www.brunobergher.com/blog/2007/10/09/new-media-guidelines-for-old-design-problems/comment-page-1/#comment-4</link>
		<dc:creator>brunobergher::blog · Past Thoughts &#187; OK, we do 3D&#8230; But how do we design for it?</dc:creator>
		<pubDate>Mon, 15 Oct 2007 21:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brunobergher.com/2007/10/09/new-media-guidelines-for-old-design-problems/#comment-4</guid>
		<description>[...] web designers (myself included) ready to design for a 3D web? It&#8217;s been not even a week since I wrote on the difficulty most of us have with articulating a new visual language that is truly unique to the web! How could we jump from no letting go of magazines and brochures to [...]</description>
		<content:encoded><![CDATA[<p>[...] web designers (myself included) ready to design for a 3D web? It&#8217;s been not even a week since I wrote on the difficulty most of us have with articulating a new visual language that is truly unique to the web! How could we jump from no letting go of magazines and brochures to [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
