<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Making the window controls go back where they belong in Ubuntu	</title>
	<atom:link href="https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/feed/" rel="self" type="application/rss+xml" />
	<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/</link>
	<description></description>
	<lastBuildDate>Sun, 03 Oct 2010 03:56:17 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.6</generator>
	<item>
		<title>
		By: BrianX		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524050</link>

		<dc:creator><![CDATA[BrianX]]></dc:creator>
		<pubDate>Sun, 03 Oct 2010 03:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524050</guid>

					<description><![CDATA[Also, re Emacs scrollbar behavior: 

I don&#039;t know the exact history, but iirc the Athena widgets were developed at a time when the GUI vocabulary was still in flux. Personally I find manipulating Athena widgets to be pointlessly complicated anyway - grab and drag with the index finger maps much more closely to meatspace object handling than Athena&#039;s strange middle button thing.

I do wonder how closely Athena behavior matches Smalltalk-80&#039;s. Squeak isn&#039;t as obvious a parallel as you&#039;d think, though it&#039;s pretty alien in its own right.]]></description>
			<content:encoded><![CDATA[<p>Also, re Emacs scrollbar behavior: </p>
<p>I don&#8217;t know the exact history, but iirc the Athena widgets were developed at a time when the GUI vocabulary was still in flux. Personally I find manipulating Athena widgets to be pointlessly complicated anyway &#8211; grab and drag with the index finger maps much more closely to meatspace object handling than Athena&#8217;s strange middle button thing.</p>
<p>I do wonder how closely Athena behavior matches Smalltalk-80&#8217;s. Squeak isn&#8217;t as obvious a parallel as you&#8217;d think, though it&#8217;s pretty alien in its own right.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: BrianX		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524049</link>

		<dc:creator><![CDATA[BrianX]]></dc:creator>
		<pubDate>Sun, 03 Oct 2010 03:41:35 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524049</guid>

					<description><![CDATA[Greg:

I suspect menu bar placement on very large screens is largely a matter of personal choice. I won&#039;t speak for all Mac users, but setting the mouse speed as fast as I can reasonably handle it works fine for me. It may be different for multiscreen setups, but I&#039;ve never been so lucky as to have that.
 ]]></description>
			<content:encoded><![CDATA[<p>Greg:</p>
<p>I suspect menu bar placement on very large screens is largely a matter of personal choice. I won&#8217;t speak for all Mac users, but setting the mouse speed as fast as I can reasonably handle it works fine for me. It may be different for multiscreen setups, but I&#8217;ve never been so lucky as to have that.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jean-Denis		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524048</link>

		<dc:creator><![CDATA[Jean-Denis]]></dc:creator>
		<pubDate>Sun, 03 Oct 2010 02:32:12 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524048</guid>

					<description><![CDATA[Finding where the item is is part of the acquisition time. Most -if not all- of that part, can be reduced through learning (familiarity). The rest of time obeys Fitts law, even if your consider it trivial.

Of course, if you don&#039;t use the menu bar, then its position doesn&#039;t matter much.

Common user testing shows that most users use it quite a bit too, even when keyboard navigation is available, except for a very few commonly used commands. Your profile is almost certainly different from Joe User&#039;s.

Now you may argue that Linux is not intended for &quot;common users&quot;, and therefore my point do not apply. I have no problem with that.

And which papers? All my papers are scanned and stored. Thereafter they occupy some real estate in a window on my screen, why I want maximized to the paper size, not more.

Having such a large screen (two of them in fact) lets me have many pieces of information on the screen at the same time, which I find invaluable for my job developing software. The last thing I want from my IDE is to cover all those windows when I maximize one of them.

]]></description>
			<content:encoded><![CDATA[<p>Finding where the item is is part of the acquisition time. Most -if not all- of that part, can be reduced through learning (familiarity). The rest of time obeys Fitts law, even if your consider it trivial.</p>
<p>Of course, if you don&#8217;t use the menu bar, then its position doesn&#8217;t matter much.</p>
<p>Common user testing shows that most users use it quite a bit too, even when keyboard navigation is available, except for a very few commonly used commands. Your profile is almost certainly different from Joe User&#8217;s.</p>
<p>Now you may argue that Linux is not intended for &#8220;common users&#8221;, and therefore my point do not apply. I have no problem with that.</p>
<p>And which papers? All my papers are scanned and stored. Thereafter they occupy some real estate in a window on my screen, why I want maximized to the paper size, not more.</p>
<p>Having such a large screen (two of them in fact) lets me have many pieces of information on the screen at the same time, which I find invaluable for my job developing software. The last thing I want from my IDE is to cover all those windows when I maximize one of them.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524047</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Sun, 03 Oct 2010 02:06:13 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524047</guid>

					<description><![CDATA[&lt;em&gt;I certainly don&#039;t want a terminal (or a text editor window) to maximize to the full width of my 2560 pixel desktop screen (nor on my 1920 pixel laptop screen for that matter).&lt;/em&gt;

If I had a really wide screen, I wouldn&#039;t want that either.  I prefer multiple regular shaped screens. 

I don&#039;t have any problem getting my mouse to hit a target, though.  And, Fitts law is about time to hit target, while my concern is knowing where the target is because I&#039;m accustom to it. I may, for instance, have preferred the windows controls on the right side (or even bottom somewhere like they are in emacs) had I been accustom to that.  

I think this may be a case of misplaced fetishizing of an efficiency that is not really important. The best use of the mouse, if you want efficiency, is to hold down your papers in a breeze while you get busy with your keyboard!  ]]></description>
			<content:encoded><![CDATA[<p><em>I certainly don&#8217;t want a terminal (or a text editor window) to maximize to the full width of my 2560 pixel desktop screen (nor on my 1920 pixel laptop screen for that matter).</em></p>
<p>If I had a really wide screen, I wouldn&#8217;t want that either.  I prefer multiple regular shaped screens. </p>
<p>I don&#8217;t have any problem getting my mouse to hit a target, though.  And, Fitts law is about time to hit target, while my concern is knowing where the target is because I&#8217;m accustom to it. I may, for instance, have preferred the windows controls on the right side (or even bottom somewhere like they are in emacs) had I been accustom to that.  </p>
<p>I think this may be a case of misplaced fetishizing of an efficiency that is not really important. The best use of the mouse, if you want efficiency, is to hold down your papers in a breeze while you get busy with your keyboard!  </p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jean-Denis		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524046</link>

		<dc:creator><![CDATA[Jean-Denis]]></dc:creator>
		<pubDate>Sun, 03 Oct 2010 01:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524046</guid>

					<description><![CDATA[Which fits with the accelerating behavior of mice: a flick of the wrist and your mouse pointer is at the edge, whatever the distance from its starting point.]]></description>
			<content:encoded><![CDATA[<p>Which fits with the accelerating behavior of mice: a flick of the wrist and your mouse pointer is at the edge, whatever the distance from its starting point.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jean-Denis		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524045</link>

		<dc:creator><![CDATA[Jean-Denis]]></dc:creator>
		<pubDate>Sun, 03 Oct 2010 01:19:42 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524045</guid>

					<description><![CDATA[Maximizing: our opinions differ somewhat after all! To use you own examples, I certainly don&#039;t want a terminal (or a text editor window) to maximize to the full width of my 2560 pixel desktop screen (nor on my 1920 pixel laptop screen for that matter).

Fitts law states that the time acquire a screen target depends both on the target size and on the target distance:

t â?? f(d/s) where t is the time, s is the target size, d is the target distance, and f is an increasing function, often taken to be a log function.

As you can imagine, when s â?? â??, then d doesn&#039;t matter.

The point is: for the top of the screen (or any edge), distance doesn&#039;t matter.
]]></description>
			<content:encoded><![CDATA[<p>Maximizing: our opinions differ somewhat after all! To use you own examples, I certainly don&#8217;t want a terminal (or a text editor window) to maximize to the full width of my 2560 pixel desktop screen (nor on my 1920 pixel laptop screen for that matter).</p>
<p>Fitts law states that the time acquire a screen target depends both on the target size and on the target distance:</p>
<p>t â?? f(d/s) where t is the time, s is the target size, d is the target distance, and f is an increasing function, often taken to be a log function.</p>
<p>As you can imagine, when s â?? â??, then d doesn&#8217;t matter.</p>
<p>The point is: for the top of the screen (or any edge), distance doesn&#8217;t matter.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524044</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Sun, 03 Oct 2010 00:26:10 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524044</guid>

					<description><![CDATA[Always maximizing to the whole screen is the behavior I want on my laptop.  On my desktop, I would like certain apps to always maximize to a particular monitor&#039;s screen, other apps to do different things, but always maximizing is not good on that computer (and since there are multiple heads, &quot;maximizing&quot; is not &quot;maximizing&quot; unless X is broken.)

Now I get what you mean about the infinite height.  Makes sense, except it is also the case that the menu is not always nearby.  Unless one always maximizes the window.  Therein lies the problem. . ]]></description>
			<content:encoded><![CDATA[<p>Always maximizing to the whole screen is the behavior I want on my laptop.  On my desktop, I would like certain apps to always maximize to a particular monitor&#8217;s screen, other apps to do different things, but always maximizing is not good on that computer (and since there are multiple heads, &#8220;maximizing&#8221; is not &#8220;maximizing&#8221; unless X is broken.)</p>
<p>Now I get what you mean about the infinite height.  Makes sense, except it is also the case that the menu is not always nearby.  Unless one always maximizes the window.  Therein lies the problem. . </p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jean-Denis		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524043</link>

		<dc:creator><![CDATA[Jean-Denis]]></dc:creator>
		<pubDate>Sat, 02 Oct 2010 22:42:03 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524043</guid>

					<description><![CDATA[&lt;i&gt;Why?&lt;/i&gt;

Because a menu bar inside a window has a finite height, which makes it a hard target to hit. While a menu bar at the top of the screen has an infinite height, and makes it easy to hit.

On my Linux-Gnome screen, the top of the screen is occupied by system menus. Application menus are in their own windows. The result is that the most often used menus are difficult to hit, while those menus that I use less often use the most precious User Interface resource: the screen edge.

This is totally screwed.

(regarding your comment re the maximizing behavior, you basically have the same opinion as mine: always maximizing to the whole screen is dumb).
]]></description>
			<content:encoded><![CDATA[<p><i>Why?</i></p>
<p>Because a menu bar inside a window has a finite height, which makes it a hard target to hit. While a menu bar at the top of the screen has an infinite height, and makes it easy to hit.</p>
<p>On my Linux-Gnome screen, the top of the screen is occupied by system menus. Application menus are in their own windows. The result is that the most often used menus are difficult to hit, while those menus that I use less often use the most precious User Interface resource: the screen edge.</p>
<p>This is totally screwed.</p>
<p>(regarding your comment re the maximizing behavior, you basically have the same opinion as mine: always maximizing to the whole screen is dumb).</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524042</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Sat, 02 Oct 2010 16:46:28 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524042</guid>

					<description><![CDATA[&lt;em&gt;But if you are really serious about Fitts law, then you despise menu bars inside windows.&lt;/em&gt;

Why?

&lt;em&gt;Maximizing to the largest area necessary to enclose all the available window content arguably is more efficient use of available screen real estate.&lt;/em&gt;

That does not make sense for a lot of applications.  More than half of what I do is done inside a text editor that starts out blank.  20 percent of what I do is done in a terminal that starts out with a prompt.  There is no pre-existing thing. Rather, there is my personal concept of what size I want the window to be when I use it.  And, I do wish that was a bit more automatically adjustable.  ]]></description>
			<content:encoded><![CDATA[<p><em>But if you are really serious about Fitts law, then you despise menu bars inside windows.</em></p>
<p>Why?</p>
<p><em>Maximizing to the largest area necessary to enclose all the available window content arguably is more efficient use of available screen real estate.</em></p>
<p>That does not make sense for a lot of applications.  More than half of what I do is done inside a text editor that starts out blank.  20 percent of what I do is done in a terminal that starts out with a prompt.  There is no pre-existing thing. Rather, there is my personal concept of what size I want the window to be when I use it.  And, I do wish that was a bit more automatically adjustable.  </p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2010/10/01/making-the-window-controls-go/#comment-524041</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Sat, 02 Oct 2010 16:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2010/10/01/making-the-window-controls-go/#comment-524041</guid>

					<description><![CDATA[Ah, excuse me... the menu bar has to have its controls on the same side as the vert. scroll bar, yes?  

I always wondered why by default, the gui version of emacs put the scroll bar on the left (though as expected this is easily changed).  ]]></description>
			<content:encoded><![CDATA[<p>Ah, excuse me&#8230; the menu bar has to have its controls on the same side as the vert. scroll bar, yes?  </p>
<p>I always wondered why by default, the gui version of emacs put the scroll bar on the left (though as expected this is easily changed).  </p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
