<?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: Which Scrollbar Navigation is Best?</title>
	<atom:link href="http://www.actionscriptartist.com/flash-and-usability/which-scrollbar-navigation-is-best/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.actionscriptartist.com/flash-and-usability/which-scrollbar-navigation-is-best/</link>
	<description>Design, create, and develop.</description>
	<lastBuildDate>Tue, 18 Aug 2009 23:02:00 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Og2t</title>
		<link>http://www.actionscriptartist.com/flash-and-usability/which-scrollbar-navigation-is-best/comment-page-1/#comment-1027</link>
		<dc:creator>Og2t</dc:creator>
		<pubDate>Tue, 18 Aug 2009 23:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.actionscriptartist.com/?p=70#comment-1027</guid>
		<description>Totally agree with Vladimir. Sometimes you just have to move on and forget about old interfaces (which traditional scrollbar is a great example of). Apart from distress, it also creates RSI (by forcing you to stretch your wrists to get to it).
But &quot;a scrollbar as an indicator of scrolled content position&quot; (like Apple&#039;s iPhone OS) is a good idea, then artist&#039;s job to style it might make sense as long as its function is obvious enough.</description>
		<content:encoded><![CDATA[<p>Totally agree with Vladimir. Sometimes you just have to move on and forget about old interfaces (which traditional scrollbar is a great example of). Apart from distress, it also creates RSI (by forcing you to stretch your wrists to get to it).<br />
But &#8220;a scrollbar as an indicator of scrolled content position&#8221; (like Apple&#8217;s iPhone OS) is a good idea, then artist&#8217;s job to style it might make sense as long as its function is obvious enough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders</title>
		<link>http://www.actionscriptartist.com/flash-and-usability/which-scrollbar-navigation-is-best/comment-page-1/#comment-1024</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Mon, 06 Apr 2009 22:49:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.actionscriptartist.com/?p=70#comment-1024</guid>
		<description>Thanks for your response Vladimir!  You have added greatly to this article.</description>
		<content:encoded><![CDATA[<p>Thanks for your response Vladimir!  You have added greatly to this article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vladimir Tsvetkov</title>
		<link>http://www.actionscriptartist.com/flash-and-usability/which-scrollbar-navigation-is-best/comment-page-1/#comment-1023</link>
		<dc:creator>Vladimir Tsvetkov</dc:creator>
		<pubDate>Sat, 04 Apr 2009 10:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.actionscriptartist.com/?p=70#comment-1023</guid>
		<description>In terms of usability none of the existing scroll-bars are  usable. Why? Let&#039;s make a bit of measuring- what it takes to use the scroll-bar:

1. Moving your hand from the keyboard to the mouse - 0.4s

2. Mental preparation - the user needs to decide whether to use the tiny buttons of the scroll-bar or to drag the scroll-thumb, or to click at the scroll-thumb - 1.35s (Why are there so many ways to make the same gesture. OK, for the sake of simplicity let&#039;s assume the user always uses the scroll-thumb)

3. Pointing - placing the mouse over the scroll-thumb - it usually takes 1.1s, but because the most common case is using a vertical scroll-bar, which is pretty tiny in width, so according to the Hick&#039;s and Fitts law (there is logarithmic relationship between the horizontal size of an interactive element and its usability) it will even take longer than 1.1s

4. Tapping the key of the pointing device to initiate the drag of the scroll-thumb - 0.2s

5. Another pointing - moving the mouse to the next position of the scroll-thumb - 1.1s

6. Mental preparation - deciding if the new position is the position that the user wants - 1.35s

5. Tapping the key - release the primary key of the pointing device - 0.2s

All it takes is - 0.4 + 1.35 + 1.1 + 0.2 + 1.1 + 1.35 + 0.2 = 5.7s

Removing completely all the scroll-bars and using gestures as the panning in the ZUIs or scrolling with the scrolling wheel will reduce this time and the psychological distress of this simple operation significantly. 

Don&#039;t want to sound arrogant, but there are no good reasons to use an artist for the interaction design (unless this artist is an expert or has deep interests in human cognetics, ergonomics and interaction design), but an artist can do miracles with making an interface aesthetically pleasing - and this is also very important for usability.</description>
		<content:encoded><![CDATA[<p>In terms of usability none of the existing scroll-bars are  usable. Why? Let&#8217;s make a bit of measuring- what it takes to use the scroll-bar:</p>
<p>1. Moving your hand from the keyboard to the mouse &#8211; 0.4s</p>
<p>2. Mental preparation &#8211; the user needs to decide whether to use the tiny buttons of the scroll-bar or to drag the scroll-thumb, or to click at the scroll-thumb &#8211; 1.35s (Why are there so many ways to make the same gesture. OK, for the sake of simplicity let&#8217;s assume the user always uses the scroll-thumb)</p>
<p>3. Pointing &#8211; placing the mouse over the scroll-thumb &#8211; it usually takes 1.1s, but because the most common case is using a vertical scroll-bar, which is pretty tiny in width, so according to the Hick&#8217;s and Fitts law (there is logarithmic relationship between the horizontal size of an interactive element and its usability) it will even take longer than 1.1s</p>
<p>4. Tapping the key of the pointing device to initiate the drag of the scroll-thumb &#8211; 0.2s</p>
<p>5. Another pointing &#8211; moving the mouse to the next position of the scroll-thumb &#8211; 1.1s</p>
<p>6. Mental preparation &#8211; deciding if the new position is the position that the user wants &#8211; 1.35s</p>
<p>5. Tapping the key &#8211; release the primary key of the pointing device &#8211; 0.2s</p>
<p>All it takes is &#8211; 0.4 + 1.35 + 1.1 + 0.2 + 1.1 + 1.35 + 0.2 = 5.7s</p>
<p>Removing completely all the scroll-bars and using gestures as the panning in the ZUIs or scrolling with the scrolling wheel will reduce this time and the psychological distress of this simple operation significantly. </p>
<p>Don&#8217;t want to sound arrogant, but there are no good reasons to use an artist for the interaction design (unless this artist is an expert or has deep interests in human cognetics, ergonomics and interaction design), but an artist can do miracles with making an interface aesthetically pleasing &#8211; and this is also very important for usability.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
