<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.12-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Thunderbird&#8217;s Ridiculous Menu Structure</title>
	<link>http://www.lshift.net/blog/2005/11/04/thunderbirds-ridiculous-menu-structure</link>
	<description>What happens at LShift</description>
	<pubDate>Tue, 06 Jan 2009 22:07:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.12-alpha</generator>

	<item>
		<title>by: chris</title>
		<link>http://www.lshift.net/blog/2005/11/04/thunderbirds-ridiculous-menu-structure#comment-312</link>
		<pubDate>Thu, 02 Feb 2006 20:29:31 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2005/11/04/thunderbirds-ridiculous-menu-structure#comment-312</guid>
					<description>&lt;p&gt;&#62; What on earth is the motivation for making the menus different like that?&lt;/p&gt;

&lt;p&gt;Or indeed, of making the menus separate at all? Far better for Compose to be within the main window, using the single menu bar. Then we wouldn;t have TB windows littering the desktop, nor the nasty problems that occur should the main Window be closed before the Compose window... !&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&gt; What on earth is the motivation for making the menus different like that?</p>
<p>Or indeed, of making the menus separate at all? Far better for Compose to be within the main window, using the single menu bar. Then we wouldn;t have TB windows littering the desktop, nor the nasty problems that occur should the main Window be closed before the Compose window&#8230; !</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: mikeb</title>
		<link>http://www.lshift.net/blog/2005/11/04/thunderbirds-ridiculous-menu-structure#comment-25</link>
		<pubDate>Mon, 07 Nov 2005 15:46:56 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2005/11/04/thunderbirds-ridiculous-menu-structure#comment-25</guid>
					<description>&lt;p&gt;Perhaps you should say ".. what's the motivation for having the menus different &lt;em&gt;like that&lt;/em&gt;?"  I expect the motivation for having them different at all is that there are menus and menu items only relevant in the compose window.&lt;/p&gt;

&lt;p&gt;On my PowerBook the main menu takes &lt;strong&gt;all&lt;/strong&gt; of the real estate (covering, for instance, the wireless status thingy), so I can perhaps understand why they would be concerned about screen real estate.  On the other hand, you're talking about menu &lt;strong&gt;items&lt;/strong&gt; missing, in a menu of about three things, which doesn't make sense at all.&lt;/p&gt;

&lt;p&gt;Also, this makes the interface more often modal, which matters especially on MacOS for which there is one menu per application.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Perhaps you should say &#8220;.. what&#8217;s the motivation for having the menus different <em>like that</em>?&#8221;  I expect the motivation for having them different at all is that there are menus and menu items only relevant in the compose window.</p>
<p>On my PowerBook the main menu takes <strong>all</strong> of the real estate (covering, for instance, the wireless status thingy), so I can perhaps understand why they would be concerned about screen real estate.  On the other hand, you&#8217;re talking about menu <strong>items</strong> missing, in a menu of about three things, which doesn&#8217;t make sense at all.</p>
<p>Also, this makes the interface more often modal, which matters especially on MacOS for which there is one menu per application.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: matthew</title>
		<link>http://www.lshift.net/blog/2005/11/04/thunderbirds-ridiculous-menu-structure#comment-23</link>
		<pubDate>Sun, 06 Nov 2005 11:07:45 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2005/11/04/thunderbirds-ridiculous-menu-structure#comment-23</guid>
					<description>&lt;p&gt;Yes, I have to say that I've yet to come across a windowing system with the consistency and intelligence of RISC OS which hasn't really had any major development since the mid 90s. I think this is why I prefer command-line applications - the interface may be clunky, but at least it's fast. A poorly designed GUI can really slow you down.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Yes, I have to say that I&#8217;ve yet to come across a windowing system with the consistency and intelligence of RISC OS which hasn&#8217;t really had any major development since the mid 90s. I think this is why I prefer command-line applications - the interface may be clunky, but at least it&#8217;s fast. A poorly designed GUI can really slow you down.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: tom berger</title>
		<link>http://www.lshift.net/blog/2005/11/04/thunderbirds-ridiculous-menu-structure#comment-22</link>
		<pubDate>Fri, 04 Nov 2005 20:10:09 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2005/11/04/thunderbirds-ridiculous-menu-structure#comment-22</guid>
					<description>&lt;p&gt;did you file a bug? from my past experience mozilla developers have been always responsive to bug reports. that's another advantage you have being a computer programmer - you can write exceptionally useful bug reports!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>did you file a bug? from my past experience mozilla developers have been always responsive to bug reports. that&#8217;s another advantage you have being a computer programmer - you can write exceptionally useful bug reports!</p>
]]></content:encoded>
				</item>
</channel>
</rss>
