<?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 or beachball</title>
	<atom:link href="http://reliablybroken.com/b/2010/05/death-or-beachball/feed/" rel="self" type="application/rss+xml" />
	<link>http://reliablybroken.com/b/2010/05/death-or-beachball/</link>
	<description>It&#039;s a blog: let&#039;s do funch!</description>
	<lastBuildDate>Sat, 04 Feb 2012 01:21:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Brett Badger</title>
		<link>http://reliablybroken.com/b/2010/05/death-or-beachball/comment-page-1/#comment-38918</link>
		<dc:creator>Brett Badger</dc:creator>
		<pubDate>Mon, 23 Jan 2012 11:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=450#comment-38918</guid>
		<description>&lt;p&gt;Thanks again for the blog article.Really looking forward to read more. Much obliged.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks again for the blog article.Really looking forward to read more. Much obliged.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://reliablybroken.com/b/2010/05/death-or-beachball/comment-page-1/#comment-844</link>
		<dc:creator>david</dc:creator>
		<pubDate>Sat, 05 Jun 2010 22:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=450#comment-844</guid>
		<description>&lt;p&gt;&lt;a href=&quot;#comment-841&quot; rel=&quot;nofollow&quot;&gt;@Matt Lundstrom&lt;/a&gt; there is certainly an argument for another cursor that indicates a long-running task that cannot be interrupted but Adobe&#039;s choice of the grey petal pinwheel is odd, and so I argued that the watch cursor would make more sense. As for belching, @Jesper was just quoting my earlier comment where I was suggesting that if Photoshop frequently showed a progress meter it would quickly become irritating.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><a href="#comment-841" rel="nofollow">@Matt Lundstrom</a> there is certainly an argument for another cursor that indicates a long-running task that cannot be interrupted but Adobe&#8217;s choice of the grey petal pinwheel is odd, and so I argued that the watch cursor would make more sense. As for belching, @Jesper was just quoting my earlier comment where I was suggesting that if Photoshop frequently showed a progress meter it would quickly become irritating.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Lundstrom</title>
		<link>http://reliablybroken.com/b/2010/05/death-or-beachball/comment-page-1/#comment-841</link>
		<dc:creator>Matt Lundstrom</dc:creator>
		<pubDate>Fri, 04 Jun 2010 18:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=450#comment-841</guid>
		<description>&lt;p&gt;When did the spinning beachball of death ever communicate excellent user feedback? When&#039;s the last time you saw SBBOD and though &quot;OK good. Everything is working fine?&quot;.&lt;/p&gt;

&lt;p&gt;If an improvement is a break from convention I&#039;m not going to discount it from being an improvement.&lt;/p&gt;

&lt;p&gt;I&#039;d argue that a wait indicator I notice is better than a wait indicator I don&#039;t. A wait indicator that only appears when a process is going A-OK is better that a wait indicator that tells me that s%$@ may or may not hit the fan.&lt;/p&gt;

&lt;p&gt;@Jesper
You could say that Photoshop gives the user feedback indicators frequently. If you wanted to spin that to make that sound like a bad thing you could call it &quot;belching&quot;. Sure.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>When did the spinning beachball of death ever communicate excellent user feedback? When&#8217;s the last time you saw SBBOD and though &#8220;OK good. Everything is working fine?&#8221;.</p>

<p>If an improvement is a break from convention I&#8217;m not going to discount it from being an improvement.</p>

<p>I&#8217;d argue that a wait indicator I notice is better than a wait indicator I don&#8217;t. A wait indicator that only appears when a process is going A-OK is better that a wait indicator that tells me that s%$@ may or may not hit the fan.</p>

<p>@Jesper
You could say that Photoshop gives the user feedback indicators frequently. If you wanted to spin that to make that sound like a bad thing you could call it &#8220;belching&#8221;. Sure.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper</title>
		<link>http://reliablybroken.com/b/2010/05/death-or-beachball/comment-page-1/#comment-840</link>
		<dc:creator>Jesper</dc:creator>
		<pubDate>Fri, 04 Jun 2010 16:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=450#comment-840</guid>
		<description>&lt;p&gt;Doesn&#039;t Photoshop already &quot;belch progress meters all over the place&quot;, though?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Doesn&#8217;t Photoshop already &#8220;belch progress meters all over the place&#8221;, though?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://reliablybroken.com/b/2010/05/death-or-beachball/comment-page-1/#comment-838</link>
		<dc:creator>david</dc:creator>
		<pubDate>Mon, 31 May 2010 21:16:15 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=450#comment-838</guid>
		<description>&lt;p&gt;&lt;a href=&quot;#comment-836&quot; rel=&quot;nofollow&quot;&gt;@Jesper&lt;/a&gt; well... I am not convinced by my own argument that the watch cursor is a better choice. The other approach Adobe could take when an action will take a significant length of time would be to display a modal dialog with a (possibly indeterminate) progress bar and just use the regular arrow cursor.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/XHIGHIDesign/XHIGHIDesign.html#//apple_ref/doc/uid/TP30000353-TPXREF106&quot; rel=&quot;nofollow&quot;&gt;Apple&#039;s guidelines recommend just that&lt;/a&gt; , but I wonder whether users would perceive Photoshop CS5 as much slower (even if it was as fast or faster) just because this hypothetical new version has started belching progress meters all over the place.&lt;/p&gt;

&lt;p&gt;And so one comes back to wanting to use a cursor which indicates progress...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><a href="#comment-836" rel="nofollow">@Jesper</a> well&#8230; I am not convinced by my own argument that the watch cursor is a better choice. The other approach Adobe could take when an action will take a significant length of time would be to display a modal dialog with a (possibly indeterminate) progress bar and just use the regular arrow cursor.</p>

<p><a href="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/XHIGHIDesign/XHIGHIDesign.html#//apple_ref/doc/uid/TP30000353-TPXREF106" rel="nofollow">Apple&#8217;s guidelines recommend just that</a> , but I wonder whether users would perceive Photoshop CS5 as much slower (even if it was as fast or faster) just because this hypothetical new version has started belching progress meters all over the place.</p>

<p>And so one comes back to wanting to use a cursor which indicates progress&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper</title>
		<link>http://reliablybroken.com/b/2010/05/death-or-beachball/comment-page-1/#comment-836</link>
		<dc:creator>Jesper</dc:creator>
		<pubDate>Mon, 31 May 2010 00:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=450#comment-836</guid>
		<description>&lt;p&gt;And to drive home another related point more explicitly: yes, the watch cursor may feel more friendly than the beachball. That&#039;s because of conditioning: the watch in OS 9 appeared everywhere, including when things were quite alright, while the beachball is designed to only show up to indicate that something may actually have gone awry.&lt;/p&gt;

&lt;p&gt;Because this upsets me, I&#039;ll point out once again how the spinner as a cursor is a way of snatching defeat from the jaws of victory. The spinner stands for a responsive UI while the things that have to go away and do some work do that; that Adobe feels it&#039;s comfortable to adopt the look, but not the feel or work of recent (as in &quot;early last decade&quot;) advancements speaks a bit too well to their selective brilliance. There&#039;s a clear, well-defined alternative, established with users, providing actual benefits and with ample precedent, and they go make shit up.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>And to drive home another related point more explicitly: yes, the watch cursor may feel more friendly than the beachball. That&#8217;s because of conditioning: the watch in OS 9 appeared everywhere, including when things were quite alright, while the beachball is designed to only show up to indicate that something may actually have gone awry.</p>

<p>Because this upsets me, I&#8217;ll point out once again how the spinner as a cursor is a way of snatching defeat from the jaws of victory. The spinner stands for a responsive UI while the things that have to go away and do some work do that; that Adobe feels it&#8217;s comfortable to adopt the look, but not the feel or work of recent (as in &#8220;early last decade&#8221;) advancements speaks a bit too well to their selective brilliance. There&#8217;s a clear, well-defined alternative, established with users, providing actual benefits and with ample precedent, and they go make shit up.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper</title>
		<link>http://reliablybroken.com/b/2010/05/death-or-beachball/comment-page-1/#comment-835</link>
		<dc:creator>Jesper</dc:creator>
		<pubDate>Mon, 31 May 2010 00:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=450#comment-835</guid>
		<description>&lt;p&gt;As far as I&#039;m concerned, the right way to handle this is by never changing the mouse cursor and by showing the spinner -- I&#039;m sorry, indeterminate progress indicator -- in a contextually informative or consistent location.&lt;/p&gt;

&lt;p&gt;The spinner is a control, not a cursor. The reason there&#039;s no spinner cursor by default is the reason the watch cursor didn&#039;t make the move to Cocoa&#039;s NSCursor -- it&#039;s not the way you&#039;re supposed to indicate that things are happening. Things are supposed to happen asynchronously. As is usually the case in Photoshop, the things that take time may well actually block progress until they&#039;re done, but you should be free to feel like you can cancel progress (and a cursor without a pointed hotspot doesn&#039;t indicate well enough that you can click something) or dick around in Preferences.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>As far as I&#8217;m concerned, the right way to handle this is by never changing the mouse cursor and by showing the spinner &#8212; I&#8217;m sorry, indeterminate progress indicator &#8212; in a contextually informative or consistent location.</p>

<p>The spinner is a control, not a cursor. The reason there&#8217;s no spinner cursor by default is the reason the watch cursor didn&#8217;t make the move to Cocoa&#8217;s NSCursor &#8212; it&#8217;s not the way you&#8217;re supposed to indicate that things are happening. Things are supposed to happen asynchronously. As is usually the case in Photoshop, the things that take time may well actually block progress until they&#8217;re done, but you should be free to feel like you can cancel progress (and a cursor without a pointed hotspot doesn&#8217;t indicate well enough that you can click something) or dick around in Preferences.</p>]]></content:encoded>
	</item>
</channel>
</rss>

