<?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: User interface thoughts</title>
	<atom:link href="http://www.kathrynhuxtable.org/blog/2009/10/03/user-interface-thoughts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kathrynhuxtable.org/blog/2009/10/03/user-interface-thoughts/</link>
	<description>Rants on computing, politics, and life</description>
	<lastBuildDate>Fri, 02 Dec 2011 19:11:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Kathryn Huxtable</title>
		<link>http://www.kathrynhuxtable.org/blog/2009/10/03/user-interface-thoughts/comment-page-1/#comment-21</link>
		<dc:creator>Kathryn Huxtable</dc:creator>
		<pubDate>Sun, 04 Oct 2009 17:58:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.kathrynhuxtable.org/blog/?p=61#comment-21</guid>
		<description>At the moment, we&#039;re setting the property and letting Aqua manage the menu bar.

It&#039;s part of being a good Mac citizen. Non Java apps seem to all use the system menu bar. Why shouldn&#039;t Java apps?</description>
		<content:encoded><![CDATA[<p>At the moment, we&#8217;re setting the property and letting Aqua manage the menu bar.</p>
<p>It&#8217;s part of being a good Mac citizen. Non Java apps seem to all use the system menu bar. Why shouldn&#8217;t Java apps?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Hunsicker</title>
		<link>http://www.kathrynhuxtable.org/blog/2009/10/03/user-interface-thoughts/comment-page-1/#comment-20</link>
		<dc:creator>Marco Hunsicker</dc:creator>
		<pubDate>Sun, 04 Oct 2009 17:54:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.kathrynhuxtable.org/blog/?p=61#comment-20</guid>
		<description>Thanks for your answers. Dynamically changing the L&amp;F is a non-issue, I believe. Not something I would worry about.

Do you always use the global menu bar Mac OS X? Or only if the corresponding system property is set?</description>
		<content:encoded><![CDATA[<p>Thanks for your answers. Dynamically changing the L&amp;F is a non-issue, I believe. Not something I would worry about.</p>
<p>Do you always use the global menu bar Mac OS X? Or only if the corresponding system property is set?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathryn Huxtable</title>
		<link>http://www.kathrynhuxtable.org/blog/2009/10/03/user-interface-thoughts/comment-page-1/#comment-19</link>
		<dc:creator>Kathryn Huxtable</dc:creator>
		<pubDate>Sun, 04 Oct 2009 16:49:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.kathrynhuxtable.org/blog/?p=61#comment-19</guid>
		<description>I should add that I&#039;ve almost never seen Vista and, in particular, Office Vista, so I&#039;m not terribly familiar with the &quot;stripe&quot;. I know keyboard-y people who hate it. My ex seems to be okay with it, though, and is a keyboard-y person.</description>
		<content:encoded><![CDATA[<p>I should add that I&#8217;ve almost never seen Vista and, in particular, Office Vista, so I&#8217;m not terribly familiar with the &#8220;stripe&#8221;. I know keyboard-y people who hate it. My ex seems to be okay with it, though, and is a keyboard-y person.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathryn Huxtable</title>
		<link>http://www.kathrynhuxtable.org/blog/2009/10/03/user-interface-thoughts/comment-page-1/#comment-18</link>
		<dc:creator>Kathryn Huxtable</dc:creator>
		<pubDate>Sun, 04 Oct 2009 16:42:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.kathrynhuxtable.org/blog/?p=61#comment-18</guid>
		<description>On a Mac we&#039;ll use the global menu bar. Everywhere else, we&#039;ll do the iTunes thing and put the menu in the title bar. This code is written and works.

Of course, on a non-Mac, the L&amp;F can&#039;t be uninstalled without disposing and recreating all the windows, and maybe not even then, because of the way undecorated JFrames work.

But how many apps that aren&#039;t designed to show off L&amp;Fs actually uninstall their default L&amp;F?</description>
		<content:encoded><![CDATA[<p>On a Mac we&#8217;ll use the global menu bar. Everywhere else, we&#8217;ll do the iTunes thing and put the menu in the title bar. This code is written and works.</p>
<p>Of course, on a non-Mac, the L&#038;F can&#8217;t be uninstalled without disposing and recreating all the windows, and maybe not even then, because of the way undecorated JFrames work.</p>
<p>But how many apps that aren&#8217;t designed to show off L&#038;Fs actually uninstall their default L&#038;F?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Hunsicker</title>
		<link>http://www.kathrynhuxtable.org/blog/2009/10/03/user-interface-thoughts/comment-page-1/#comment-17</link>
		<dc:creator>Marco Hunsicker</dc:creator>
		<pubDate>Sun, 04 Oct 2009 16:26:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.kathrynhuxtable.org/blog/?p=61#comment-17</guid>
		<description>I&#039;m very curious how you will tackle platform differences like global menu vs. per window menu bar. IMHO the unified tool bar appearance in Mac OS X looks and feels awesome, but one important aspect is that no menu bar items pollute the appearance. Recent Windows versions use an interesting approach and sometimes simply don&#039;t display the menu bar by default, but when using a Gnome desktop there is no (usable) counterpart. I guess some sort of dynamic adjustment is warranted here which might alienate some potential users that want a true cross-platform look.

I would second Ken&#039;s remarks about looking good. If the app looks awesome (and works great of course), most users won&#039;t care much about minor differences in appearance. After all, the application still uses the same concepts.</description>
		<content:encoded><![CDATA[<p>I&#8217;m very curious how you will tackle platform differences like global menu vs. per window menu bar. IMHO the unified tool bar appearance in Mac OS X looks and feels awesome, but one important aspect is that no menu bar items pollute the appearance. Recent Windows versions use an interesting approach and sometimes simply don&#8217;t display the menu bar by default, but when using a Gnome desktop there is no (usable) counterpart. I guess some sort of dynamic adjustment is warranted here which might alienate some potential users that want a true cross-platform look.</p>
<p>I would second Ken&#8217;s remarks about looking good. If the app looks awesome (and works great of course), most users won&#8217;t care much about minor differences in appearance. After all, the application still uses the same concepts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Orr</title>
		<link>http://www.kathrynhuxtable.org/blog/2009/10/03/user-interface-thoughts/comment-page-1/#comment-16</link>
		<dc:creator>Ken Orr</dc:creator>
		<pubDate>Sun, 04 Oct 2009 14:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.kathrynhuxtable.org/blog/?p=61#comment-16</guid>
		<description>I think that iTunes doesn&#039;t stick out because it uses the same window chrome. But even when apps do use different window chrome (think &lt;a href=&quot;http://www.pixelmator.com/&quot; rel=&quot;nofollow&quot;&gt;Pixelmator&lt;/a&gt;), they can still be acceptable to the end user. So what is it that makes it acceptable? My feeling is that as long as the application looks as good as, or better than native apps, then it doesn&#039;t much matter how different it is than native apps. For example, &lt;a href=&quot;http://tryit.adobe.com/us/photoshopelements/?sdid=EQAAM&quot; rel=&quot;nofollow&quot;&gt;Photoshop Elements&lt;/a&gt; on Windows doesn&#039;t use standard controls, but it seems that users are accepting of the app because it shows at least as much polish as native Windows apps.</description>
		<content:encoded><![CDATA[<p>I think that iTunes doesn&#8217;t stick out because it uses the same window chrome. But even when apps do use different window chrome (think <a href="http://www.pixelmator.com/" rel="nofollow">Pixelmator</a>), they can still be acceptable to the end user. So what is it that makes it acceptable? My feeling is that as long as the application looks as good as, or better than native apps, then it doesn&#8217;t much matter how different it is than native apps. For example, <a href="http://tryit.adobe.com/us/photoshopelements/?sdid=EQAAM" rel="nofollow">Photoshop Elements</a> on Windows doesn&#8217;t use standard controls, but it seems that users are accepting of the app because it shows at least as much polish as native Windows apps.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

