<?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: Death to dialog!</title>
	<atom:link href="http://gomez-rosado.com/2006/01/death-to-dialog/feed/" rel="self" type="application/rss+xml" />
	<link>http://gomez-rosado.com/2006/01/death-to-dialog/</link>
	<description></description>
	<lastBuildDate>Sat, 13 Dec 2008 08:24:37 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MalkEvange</title>
		<link>http://gomez-rosado.com/2006/01/death-to-dialog/comment-page-1/#comment-9</link>
		<dc:creator>MalkEvange</dc:creator>
		<pubDate>Mon, 06 Aug 2007 19:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://gomez-rosado.com/instinctaneous/2006/01/08/death-to-dialog/#comment-9</guid>
		<description>Interesting article!
Where can I find more on this theme?</description>
		<content:encoded><![CDATA[<p>Interesting article!<br />
Where can I find more on this theme?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: victor</title>
		<link>http://gomez-rosado.com/2006/01/death-to-dialog/comment-page-1/#comment-8</link>
		<dc:creator>victor</dc:creator>
		<pubDate>Sun, 14 Jan 2007 21:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://gomez-rosado.com/instinctaneous/2006/01/08/death-to-dialog/#comment-8</guid>
		<description>interesting approach...

but for me the keyword is &quot;switching&quot; (a word you use extensively within the article)

i agree, applications can easily adopt the &quot;switch to finder&quot; model, but (and a &#039;huge&#039; but) can the user do the same?

can the user adapt to the switch application model? i firmly believe he/she won&#039;t and i am on his/her side, until OSes find a more intuitive way to &quot;let you know where you are&quot;.

even without your &quot;switch&quot; model, users get lost in the myriad of open windows.

so perhaps the key element should (and shall) be something that links the application with the finder window (in this example). and that is exactly what the dialog box does (and beautifully in OSX, where the open/save dialog is not just linked to the application, but the file itself.

i think another approach cluld be to take the little proxy icon on the file top bar and drag it to the finder icon on the dashboard, meaning &quot;i want to save this file&quot;. in this case, no &quot;switching&quot; could confuse the user, and the gesture will mean exactly what you want it to mean: to save the file.

what do you think?</description>
		<content:encoded><![CDATA[<p>interesting approach&#8230;</p>
<p>but for me the keyword is &#8220;switching&#8221; (a word you use extensively within the article)</p>
<p>i agree, applications can easily adopt the &#8220;switch to finder&#8221; model, but (and a &#8216;huge&#8217; but) can the user do the same?</p>
<p>can the user adapt to the switch application model? i firmly believe he/she won&#8217;t and i am on his/her side, until OSes find a more intuitive way to &#8220;let you know where you are&#8221;.</p>
<p>even without your &#8220;switch&#8221; model, users get lost in the myriad of open windows.</p>
<p>so perhaps the key element should (and shall) be something that links the application with the finder window (in this example). and that is exactly what the dialog box does (and beautifully in OSX, where the open/save dialog is not just linked to the application, but the file itself.</p>
<p>i think another approach cluld be to take the little proxy icon on the file top bar and drag it to the finder icon on the dashboard, meaning &#8220;i want to save this file&#8221;. in this case, no &#8220;switching&#8221; could confuse the user, and the gesture will mean exactly what you want it to mean: to save the file.</p>
<p>what do you think?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
