<?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: The Curious Case of the Gmail Buttons</title>
	<atom:link href="http://www.andersramsay.com/2009/02/07/the-curious-case-of-the-gmail-buttons/feed" rel="self" type="application/rss+xml" />
	<link>http://www.andersramsay.com/2009/02/07/the-curious-case-of-the-gmail-buttons</link>
	<description>designing user experiences</description>
	<lastBuildDate>Tue, 31 Jan 2012 23:48:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jon</title>
		<link>http://www.andersramsay.com/2009/02/07/the-curious-case-of-the-gmail-buttons/comment-page-1#comment-70620</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 09 Jan 2012 16:41:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.andersramsay.com/?p=351#comment-70620</guid>
		<description>I&#039;ve lost my buttons altogether - well... there are three of them present (without any labels to identify them visually). They seem to work OK when I hover over them with the mouse I can identify them (preview shows what they are) but they are essentially &quot;blind click&quot; buttons now - Anyone else have this problem?  Solution? I&#039;m running updated MSW7 and always update my computer regularly... not sure what happened but the new &quot;look&quot; isn&#039;t helping me much at the moment.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve lost my buttons altogether &#8211; well&#8230; there are three of them present (without any labels to identify them visually). They seem to work OK when I hover over them with the mouse I can identify them (preview shows what they are) but they are essentially &#8220;blind click&#8221; buttons now &#8211; Anyone else have this problem?  Solution? I&#8217;m running updated MSW7 and always update my computer regularly&#8230; not sure what happened but the new &#8220;look&#8221; isn&#8217;t helping me much at the moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders</title>
		<link>http://www.andersramsay.com/2009/02/07/the-curious-case-of-the-gmail-buttons/comment-page-1#comment-11430</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Sun, 08 Feb 2009 14:24:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.andersramsay.com/?p=351#comment-11430</guid>
		<description>Hi Damon - I&#039;m going to check out &lt;a href=&quot;http://www.amazon.com/Information-Dashboard-Design-Effective-Communication/dp/0596100167&quot; rel=&quot;nofollow&quot;&gt;Information Dashboard Design&lt;/a&gt;.  Looks like an interesting read.

On one hand, I definitely agree that use of icons would make something like a delete button pop, such as using a trash can or a red circle with an &#039;x&#039; in it or whatever.  I&#039;m guessing one reason they didn&#039;t use icons don&#039;t scale that well and get less useful for less common operations, such as &quot;Mark as Read&quot; - a Labs feature I added - not sure what the icon would be for that.</description>
		<content:encoded><![CDATA[<p>Hi Damon &#8211; I&#8217;m going to check out <a href="http://www.amazon.com/Information-Dashboard-Design-Effective-Communication/dp/0596100167" rel="nofollow">Information Dashboard Design</a>.  Looks like an interesting read.</p>
<p>On one hand, I definitely agree that use of icons would make something like a delete button pop, such as using a trash can or a red circle with an &#8216;x&#8217; in it or whatever.  I&#8217;m guessing one reason they didn&#8217;t use icons don&#8217;t scale that well and get less useful for less common operations, such as &#8220;Mark as Read&#8221; &#8211; a Labs feature I added &#8211; not sure what the icon would be for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damon Poole</title>
		<link>http://www.andersramsay.com/2009/02/07/the-curious-case-of-the-gmail-buttons/comment-page-1#comment-11409</link>
		<dc:creator>Damon Poole</dc:creator>
		<pubDate>Sun, 08 Feb 2009 03:57:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.andersramsay.com/?p=351#comment-11409</guid>
		<description>I don&#039;t remember which book I got this concept from, perhaps &quot;Information Dashboard Design&quot; which shouldn&#039;t contain the word dashboard as it is a great book whether you want to do dashboards or not, but basically if you have them flush, your eye/brain can&#039;t help you. Your eye/brain can do amazing things for you almost instantaneously without you consciously thinking about it for things that match certain criteria for patterns. And when you ignore these things in your design, the user ends up having to use their slow conscious thinking process. &quot;Let&#039;s see, that&#039;s a button I guess, but it isn&#039;t delete, how about the next section?&quot;

Personally, I think they should use some icons because then your eye/brain can *really* help you out: no slow reading is required.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t remember which book I got this concept from, perhaps &#8220;Information Dashboard Design&#8221; which shouldn&#8217;t contain the word dashboard as it is a great book whether you want to do dashboards or not, but basically if you have them flush, your eye/brain can&#8217;t help you. Your eye/brain can do amazing things for you almost instantaneously without you consciously thinking about it for things that match certain criteria for patterns. And when you ignore these things in your design, the user ends up having to use their slow conscious thinking process. &#8220;Let&#8217;s see, that&#8217;s a button I guess, but it isn&#8217;t delete, how about the next section?&#8221;</p>
<p>Personally, I think they should use some icons because then your eye/brain can *really* help you out: no slow reading is required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders</title>
		<link>http://www.andersramsay.com/2009/02/07/the-curious-case-of-the-gmail-buttons/comment-page-1#comment-11383</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Sat, 07 Feb 2009 17:49:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.andersramsay.com/?p=351#comment-11383</guid>
		<description>My understanding of &lt;a href=&quot;http://en.wikipedia.org/wiki/Fitts%27_law&quot; rel=&quot;nofollow&quot;&gt;Fitts Law&lt;/a&gt; is that it relates to targeting in relationship to size and distance. I guess this could be interpreted to imply that there should be no distance between buttons.  But it would seem as if other factors are at play here, such as the ability to visually distinguish where one button ends and another begins.  The current design, with a 1-pixel border, doesn&#039;t make that easy at all.   In other words, when I want to use the delete button, it is not so much an issue of being able to target the button with my mouse, and really more an issue of being able to &lt;em&gt;see&lt;/em&gt; where it is.  Applying Fitts law, then, the decision to place the buttons flush against one another should perhaps have been accompanied by also making them somewhat larger.</description>
		<content:encoded><![CDATA[<p>My understanding of <a href="http://en.wikipedia.org/wiki/Fitts%27_law" rel="nofollow">Fitts Law</a> is that it relates to targeting in relationship to size and distance. I guess this could be interpreted to imply that there should be no distance between buttons.  But it would seem as if other factors are at play here, such as the ability to visually distinguish where one button ends and another begins.  The current design, with a 1-pixel border, doesn&#8217;t make that easy at all.   In other words, when I want to use the delete button, it is not so much an issue of being able to target the button with my mouse, and really more an issue of being able to <em>see</em> where it is.  Applying Fitts law, then, the decision to place the buttons flush against one another should perhaps have been accompanied by also making them somewhat larger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Fahey</title>
		<link>http://www.andersramsay.com/2009/02/07/the-curious-case-of-the-gmail-buttons/comment-page-1#comment-11381</link>
		<dc:creator>Christopher Fahey</dc:creator>
		<pubDate>Sat, 07 Feb 2009 17:28:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.andersramsay.com/?p=351#comment-11381</guid>
		<description>Fitt&#039;s Law, in fact, suggests that menu buttons *should* be flush against each other, preventing another kind of micro-annoyance -- missing a button entirely because you&#039;ve clicked on the small gap in between them, or just plain spending extra time aiming at a button and avoiding clicking the gap between the buttons. I&#039;ve long been of the school of thought that moving from one button to another in a toolbar or menu area should produce no flashing cursors and no &quot;dead spaces&quot; between buttons. This structure should absolutely be combined with a clear rollover state behavior indicating which button you are rolling over (I don&#039;t use gmail so I don&#039;t know if the new or old UI had this) -- this corrects errors of pressing the wrong button better than simply putting a safety gap between the buttons.</description>
		<content:encoded><![CDATA[<p>Fitt&#8217;s Law, in fact, suggests that menu buttons *should* be flush against each other, preventing another kind of micro-annoyance &#8212; missing a button entirely because you&#8217;ve clicked on the small gap in between them, or just plain spending extra time aiming at a button and avoiding clicking the gap between the buttons. I&#8217;ve long been of the school of thought that moving from one button to another in a toolbar or menu area should produce no flashing cursors and no &#8220;dead spaces&#8221; between buttons. This structure should absolutely be combined with a clear rollover state behavior indicating which button you are rolling over (I don&#8217;t use gmail so I don&#8217;t know if the new or old UI had this) &#8212; this corrects errors of pressing the wrong button better than simply putting a safety gap between the buttons.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

