<?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: Facelift</title>
	<atom:link href="http://blog.wilsonet.com/archives/2006/09/16/facelift/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wilsonet.com/archives/2006/09/16/facelift/</link>
	<description>Interaction and interface design, technology, politics, music, and random thoughts...</description>
	<lastBuildDate>Wed, 04 Nov 2009 21:08:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Drew Hamlin</title>
		<link>http://blog.wilsonet.com/archives/2006/09/16/facelift/comment-page-1/#comment-30992</link>
		<dc:creator>Drew Hamlin</dc:creator>
		<pubDate>Sun, 17 Sep 2006 04:04:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wilsonet.com/archives/2006/09/16/facelift/#comment-30992</guid>
		<description>While design decisions are just that (reflections, scroll bar appearances, etc.), it would probably be a good idea to file individual radars on things such as shift+scroll, contextual menus, command key shortcuts, Yes/No dialogs, etc.

I can assure you from first-hand experience that 3rd-party radars not only are treated like first class bugs, but they also honestly do make change happen.</description>
		<content:encoded><![CDATA[<p>While design decisions are just that (reflections, scroll bar appearances, etc.), it would probably be a good idea to file individual radars on things such as shift+scroll, contextual menus, command key shortcuts, Yes/No dialogs, etc.</p>
<p>I can assure you from first-hand experience that 3rd-party radars not only are treated like first class bugs, but they also honestly do make change happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SuitCase</title>
		<link>http://blog.wilsonet.com/archives/2006/09/16/facelift/comment-page-1/#comment-30990</link>
		<dc:creator>SuitCase</dc:creator>
		<pubDate>Sun, 17 Sep 2006 03:49:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wilsonet.com/archives/2006/09/16/facelift/#comment-30990</guid>
		<description>Good observations!

I am dismayed that you aren&#039;t immediately critical of all the new widget styles and random assortment of colours. Just because it&#039;s inoffensive doesn&#039;t mean it&#039;s okay - if Apple thinks this new alternate row colour is the best, it should be an OS X-wide change.

I&#039;m also saddened that iTunes 7 is still based on a foundation of a pokey SoundJam skin. It needs to be Cocoa (or at least made in Interface Builder) and fast - have you seen how bad this app looks in a higher-dpi on Leopard?</description>
		<content:encoded><![CDATA[<p>Good observations!</p>
<p>I am dismayed that you aren&#8217;t immediately critical of all the new widget styles and random assortment of colours. Just because it&#8217;s inoffensive doesn&#8217;t mean it&#8217;s okay &#8211; if Apple thinks this new alternate row colour is the best, it should be an OS X-wide change.</p>
<p>I&#8217;m also saddened that iTunes 7 is still based on a foundation of a pokey SoundJam skin. It needs to be Cocoa (or at least made in Interface Builder) and fast &#8211; have you seen how bad this app looks in a higher-dpi on Leopard?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
