<?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"
	>
<channel>
	<title>Comments on: Dialog Boxes: Making simple things simple&#8230;</title>
	<atom:link href="http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/</link>
	<description>pretty design pending</description>
	<pubDate>Mon, 13 Oct 2008 22:15:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: victor</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-28243</link>
		<dc:creator>victor</dc:creator>
		<pubDate>Wed, 08 Aug 2007 19:46:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-28243</guid>
		<description>I personally think it solves one little situation I have found myself in for ages: If you don't read the text (many people don't read it) it still gives you an actable button with a message that *might* be understood. Not making it a political case, but I think it, in some cases, is still better than Yes or No, and if you read it, well, you might know better. (Actually, after an application upgrade, while I'm filling some website or application data form, I really "like" when it appears, letting me know he can handle a password I might have already forgotten!)

If you make it "Don't add all keychains" and "Add all keychains" could improve, though.

I think.

(About the "Details" I don't personally find them that instructive after the first time, but then it is just me, not a pleaded case)</description>
		<content:encoded><![CDATA[<p>I personally think it solves one little situation I have found myself in for ages: If you don&#8217;t read the text (many people don&#8217;t read it) it still gives you an actable button with a message that *might* be understood. Not making it a political case, but I think it, in some cases, is still better than Yes or No, and if you read it, well, you might know better. (Actually, after an application upgrade, while I&#8217;m filling some website or application data form, I really &#8220;like&#8221; when it appears, letting me know he can handle a password I might have already forgotten!)</p>
<p>If you make it &#8220;Don&#8217;t add all keychains&#8221; and &#8220;Add all keychains&#8221; could improve, though.</p>
<p>I think.</p>
<p>(About the &#8220;Details&#8221; I don&#8217;t personally find them that instructive after the first time, but then it is just me, not a pleaded case)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donna</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-24871</link>
		<dc:creator>Donna</dc:creator>
		<pubDate>Wed, 18 Jul 2007 00:25:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-24871</guid>
		<description>I've really messed up my keychain at different times, as I keep forgetting which is the "right answer" to DON'T CHANGE or CHANGE ALL.  Such a sophisticated OS, you'd think this would not be an issue.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve really messed up my keychain at different times, as I keep forgetting which is the &#8220;right answer&#8221; to DON&#8217;T CHANGE or CHANGE ALL.  Such a sophisticated OS, you&#8217;d think this would not be an issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 90 Percent of Everything &#187; Blog Archive &#187; A great example of bad dialog box design - Part 2.</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-22751</link>
		<dc:creator>90 Percent of Everything &#187; Blog Archive &#187; A great example of bad dialog box design - Part 2.</dc:creator>
		<pubDate>Tue, 03 Jul 2007 12:22:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-22751</guid>
		<description>[...] I&#8217;ve also just realised that this has been blogged about elsewhere, with some great comment discussions. Read more here, here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve also just realised that this has been blogged about elsewhere, with some great comment discussions. Read more here, here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: UIE Brain Sparks &#187; Blog Archive &#187; Error Messages: Paying Attention to the Little Things</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-20374</link>
		<dc:creator>UIE Brain Sparks &#187; Blog Archive &#187; Error Messages: Paying Attention to the Little Things</dc:creator>
		<pubDate>Fri, 15 Jun 2007 17:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-20374</guid>
		<description>[...] You can read Leisa&#8217;s entire post here: Dialog Boxes &#8212; Making simple things simple… [...]</description>
		<content:encoded><![CDATA[<p>[...] You can read Leisa&#8217;s entire post here: Dialog Boxes &#8212; Making simple things simple… [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-20246</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Thu, 14 Jun 2007 17:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-20246</guid>
		<description>It seems to me that buttons should be labelled with actions - because you click them to do something - and "yes" and "no" are clearly not actions. It might be better if the buttons were labelled "Allow access" and "Disallow access" and the text changed accordingly.</description>
		<content:encoded><![CDATA[<p>It seems to me that buttons should be labelled with actions - because you click them to do something - and &#8220;yes&#8221; and &#8220;no&#8221; are clearly not actions. It might be better if the buttons were labelled &#8220;Allow access&#8221; and &#8220;Disallow access&#8221; and the text changed accordingly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: disambiguity - &#187; The Halo Effect - Why Apple gets away with rubbish interaction design</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-20236</link>
		<dc:creator>disambiguity - &#187; The Halo Effect - Why Apple gets away with rubbish interaction design</dc:creator>
		<pubDate>Thu, 14 Jun 2007 16:30:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-20236</guid>
		<description>[...] This is not a post about the things that Apple does badly though (although, seriously - can we get past the one button mouse already? and I do think that dialog box is pretty shocking, and those little triangles that so often hide much of the information I&#8217;m looking for in Mac applications&#8230;. please!). This is a post about what Apple does well, and how this helps them get away with doing some things not so well. [...]</description>
		<content:encoded><![CDATA[<p>[...] This is not a post about the things that Apple does badly though (although, seriously - can we get past the one button mouse already? and I do think that dialog box is pretty shocking, and those little triangles that so often hide much of the information I&#8217;m looking for in Mac applications&#8230;. please!). This is a post about what Apple does well, and how this helps them get away with doing some things not so well. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alessandra</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-19224</link>
		<dc:creator>alessandra</dc:creator>
		<pubDate>Mon, 04 Jun 2007 23:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-19224</guid>
		<description>As a new Mac user, I spent minutes trying to figure out what I should answer, the first time I was faced with that. I'm so happy somebody else got puzzled ;)</description>
		<content:encoded><![CDATA[<p>As a new Mac user, I spent minutes trying to figure out what I should answer, the first time I was faced with that. I&#8217;m so happy somebody else got puzzled <img src='http://www.disambiguity.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Lechner</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-19007</link>
		<dc:creator>Andreas Lechner</dc:creator>
		<pubDate>Fri, 01 Jun 2007 19:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-19007</guid>
		<description>We are using wireframes to specify the text of dialogue boxes - sometimes also wording lists (including error messages).
Here's my blog post on this: http://requirements.blogger.de/stories/807523/</description>
		<content:encoded><![CDATA[<p>We are using wireframes to specify the text of dialogue boxes - sometimes also wording lists (including error messages).<br />
Here&#8217;s my blog post on this: <a href="http://requirements.blogger.de/stories/807523/" rel="nofollow">http://requirements.blogger.de/stories/807523/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pauric</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-18991</link>
		<dc:creator>Pauric</dc:creator>
		<pubDate>Fri, 01 Jun 2007 12:42:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-18991</guid>
		<description>Headline: Shock Horror!!! Macs are developed by humans who make mistakes!!!

Leisa, seriously, for every stupid dialog box on os X there's got to be 5 on XP.  For every engineering centric app on a Mac there might be 5 on Linux.

Nothings perfect, but if you're having such a hard time then dump the Mac, get back on the XP pony and get back to writing great posts!!!  Dialog box usability reports is sooo beneath you. (o;</description>
		<content:encoded><![CDATA[<p>Headline: Shock Horror!!! Macs are developed by humans who make mistakes!!!</p>
<p>Leisa, seriously, for every stupid dialog box on os X there&#8217;s got to be 5 on XP.  For every engineering centric app on a Mac there might be 5 on Linux.</p>
<p>Nothings perfect, but if you&#8217;re having such a hard time then dump the Mac, get back on the XP pony and get back to writing great posts!!!  Dialog box usability reports is sooo beneath you. (o;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Medero</title>
		<link>http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-18751</link>
		<dc:creator>Shawn Medero</dc:creator>
		<pubDate>Tue, 29 May 2007 13:51:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/dialogue-boxes-making-simple-things-simple/#comment-18751</guid>
		<description>As a long time user of various desktop environments: BeOS, GNOME, KDE, Mac OS, Mac OS X, NeXT, Newton, Windows.... Apple's approach has tended to be the most consistent and least frustrating. 

Mac OS X is a bit of step back in spots when it comes to consistency though as the NeXT and Mac OS folks (along with the desire to appeal Windows converts) are battling out in development groups that often don't communicate very well.  Likewise Mac OS X has had to grow up in age where internet UI and visual elements are seemingly taken over in all forms of media regardless of how poorly they might rank in a closed scientific environment.

Still none of these excuses are worthy reasons for Apple to completely fall over itself in UI design. I think if Apple had a more transparent issue tracking process it could leverage that along with the active user base to help find and solve many of these "minor" UI glitches. ("minor" in that... when you encounter several of them a day, it is eventually becomes quite frustrating.)</description>
		<content:encoded><![CDATA[<p>As a long time user of various desktop environments: BeOS, GNOME, KDE, Mac OS, Mac OS X, NeXT, Newton, Windows&#8230;. Apple&#8217;s approach has tended to be the most consistent and least frustrating. </p>
<p>Mac OS X is a bit of step back in spots when it comes to consistency though as the NeXT and Mac OS folks (along with the desire to appeal Windows converts) are battling out in development groups that often don&#8217;t communicate very well.  Likewise Mac OS X has had to grow up in age where internet UI and visual elements are seemingly taken over in all forms of media regardless of how poorly they might rank in a closed scientific environment.</p>
<p>Still none of these excuses are worthy reasons for Apple to completely fall over itself in UI design. I think if Apple had a more transparent issue tracking process it could leverage that along with the active user base to help find and solve many of these &#8220;minor&#8221; UI glitches. (&#8221;minor&#8221; in that&#8230; when you encounter several of them a day, it is eventually becomes quite frustrating.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
