<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Glaringly obvious usability omissions</title>
	<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/</link>
	<description></description>
	<pubDate>Fri, 09 Jan 2009 01:17:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Eugenia</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4135</link>
		<author>Eugenia</author>
		<pubDate>Wed, 26 Sep 2007 01:11:03 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4135</guid>
		<description>Please me? That'd be hard. ;)</description>
		<content:encoded><![CDATA[<p>Please me? That&#8217;d be hard. <img src='http://eugenia.gnomefiles.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Bockover</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4134</link>
		<author>Aaron Bockover</author>
		<pubDate>Tue, 25 Sep 2007 23:11:03 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4134</guid>
		<description>I'm sorry I can't please you. I did what I could immediately to resolve the biggest issue. I'll direct the proper maintainers to your mockups and observations.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry I can&#8217;t please you. I did what I could immediately to resolve the biggest issue. I&#8217;ll direct the proper maintainers to your mockups and observations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eugenia</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4133</link>
		<author>Eugenia</author>
		<pubDate>Tue, 25 Sep 2007 21:38:19 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4133</guid>
		<description>Aaron, this only fixes the bold font issue. It is still difficult to distinguish quickly what is what in that window. For example, originally I did not immediately figure out that the Apps/docs/places buttons change the apps view below them! They felt that they were SEARCH's attributes! If it wasn't for my husband to point that out, I would not have figure it out just by looking at the pic. They are just disjoined.

Please check my updated mockup.</description>
		<content:encoded><![CDATA[<p>Aaron, this only fixes the bold font issue. It is still difficult to distinguish quickly what is what in that window. For example, originally I did not immediately figure out that the Apps/docs/places buttons change the apps view below them! They felt that they were SEARCH&#8217;s attributes! If it wasn&#8217;t for my husband to point that out, I would not have figure it out just by looking at the pic. They are just disjoined.</p>
<p>Please check my updated mockup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Bockover</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4132</link>
		<author>Aaron Bockover</author>
		<pubDate>Tue, 25 Sep 2007 21:32:52 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4132</guid>
		<description>Eugenia: This is indeed a theme issue, but it was broken in the old Gilouche theme. I have fixed Gilouche and committed it upstream. We will do our best to slip a new release in for 10.3 before the final release, but it is very, very late in the process. If we can't slip it in, we will ship it as an update shortly after the release.

Here's how the Main Menu looks with the fixed &lt;a href="http://abock.org/~aaron/slab.png" rel="nofollow"&gt;Gilouche theme&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Eugenia: This is indeed a theme issue, but it was broken in the old Gilouche theme. I have fixed Gilouche and committed it upstream. We will do our best to slip a new release in for 10.3 before the final release, but it is very, very late in the process. If we can&#8217;t slip it in, we will ship it as an update shortly after the release.</p>
<p>Here&#8217;s how the Main Menu looks with the fixed <a href="http://abock.org/~aaron/slab.png" rel="nofollow">Gilouche theme</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Bockover</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4117</link>
		<author>Aaron Bockover</author>
		<pubDate>Tue, 25 Sep 2007 01:31:02 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4117</guid>
		<description>Fine. Just pointing it out. The difference is that there is no product or organization called GNU/Linux. openSUSE is actually a real product, a community, a brand. SuSE used to be. It is not any more, hence my correction.

I will take a new screenshot tomorrow and link to it here.</description>
		<content:encoded><![CDATA[<p>Fine. Just pointing it out. The difference is that there is no product or organization called GNU/Linux. openSUSE is actually a real product, a community, a brand. SuSE used to be. It is not any more, hence my correction.</p>
<p>I will take a new screenshot tomorrow and link to it here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eugenia</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4116</link>
		<author>Eugenia</author>
		<pubDate>Tue, 25 Sep 2007 00:39:35 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4116</guid>
		<description>I now link to your post. Also, I don't think it's the theme's issue, but a real usability issue (please upload a new shot with the DEFAULT theme). I filed a bug report about a similar thing on Novell's bugzilla over a year ago, no one followed up. Same on gnome's bugzilla, no one followed up.

As for the actual name of SuSE these days, I don't really care (although of course I am aware of it). I just call it SuSE, just like I call GNU/Linux as Linux and Windows XP as WinXP.</description>
		<content:encoded><![CDATA[<p>I now link to your post. Also, I don&#8217;t think it&#8217;s the theme&#8217;s issue, but a real usability issue (please upload a new shot with the DEFAULT theme). I filed a bug report about a similar thing on Novell&#8217;s bugzilla over a year ago, no one followed up. Same on gnome&#8217;s bugzilla, no one followed up.</p>
<p>As for the actual name of SuSE these days, I don&#8217;t really care (although of course I am aware of it). I just call it SuSE, just like I call GNU/Linux as Linux and Windows XP as WinXP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Bockover</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4115</link>
		<author>Aaron Bockover</author>
		<pubDate>Tue, 25 Sep 2007 00:29:44 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4115</guid>
		<description>Apologies for the third comment, but I just wanted to say that I do like the idea of the user photo/login information in the top right. I will bring this up with the main menu maintainer.</description>
		<content:encoded><![CDATA[<p>Apologies for the third comment, but I just wanted to say that I do like the idea of the user photo/login information in the top right. I will bring this up with the main menu maintainer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Bockover</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4114</link>
		<author>Aaron Bockover</author>
		<pubDate>Tue, 25 Sep 2007 00:28:19 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4114</guid>
		<description>Also, it's openSUSE, not SuSE. We did technically change the name/casing, etc. a couple of years ago. JFYI.</description>
		<content:encoded><![CDATA[<p>Also, it&#8217;s openSUSE, not SuSE. We did technically change the name/casing, etc. a couple of years ago. JFYI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Bockover</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4112</link>
		<author>Aaron Bockover</author>
		<pubDate>Tue, 25 Sep 2007 00:26:30 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4112</guid>
		<description>It would be nicer if you linked to my post instead of just my screenshot. If I hadn't looked at my incoming links (vs trackbacks to the post itself, which would allow some form of context/connection between our posts), I never would have noticed your ranting on this and would not have been able to offer some different perspective/context.

As I mentioned in my reply to your comment, again, on my post, the issue is most likely a problem the the *theme* (and if you had also referenced the post, again, you may have indirectly informed you readers that I was using a custom theme). The main menu itself is in all likelihood not the culprit here as most of its elements can be themed through GTK.

In SLED at least I remember the font sizes of the elements in question being bold and larger.

Calm down. At the core, this is a usability issue, from the perspective of my screenshot, but please be careful when pointing the finger so quickly.</description>
		<content:encoded><![CDATA[<p>It would be nicer if you linked to my post instead of just my screenshot. If I hadn&#8217;t looked at my incoming links (vs trackbacks to the post itself, which would allow some form of context/connection between our posts), I never would have noticed your ranting on this and would not have been able to offer some different perspective/context.</p>
<p>As I mentioned in my reply to your comment, again, on my post, the issue is most likely a problem the the *theme* (and if you had also referenced the post, again, you may have indirectly informed you readers that I was using a custom theme). The main menu itself is in all likelihood not the culprit here as most of its elements can be themed through GTK.</p>
<p>In SLED at least I remember the font sizes of the elements in question being bold and larger.</p>
<p>Calm down. At the core, this is a usability issue, from the perspective of my screenshot, but please be careful when pointing the finger so quickly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alessandro</title>
		<link>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4111</link>
		<author>Alessandro</author>
		<pubDate>Tue, 25 Sep 2007 00:08:19 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2007/09/24/glaringly-obvious-usability-omissions/#comment-4111</guid>
		<description>that would definitely be nice, and I'd like to see it implemented. But actually I think it's not that bad: the default menu is almost empty (4 apps maybe? and no recent apps). When a user click for the first time on a non-fav app, it shows later under the new label, distant enough to realize that it's a separate group. For what concern the control-center, i totally agree with you (maybe Novell developers are just cheking their own bugzilla?)</description>
		<content:encoded><![CDATA[<p>that would definitely be nice, and I&#8217;d like to see it implemented. But actually I think it&#8217;s not that bad: the default menu is almost empty (4 apps maybe? and no recent apps). When a user click for the first time on a non-fav app, it shows later under the new label, distant enough to realize that it&#8217;s a separate group. For what concern the control-center, i totally agree with you (maybe Novell developers are just cheking their own bugzilla?)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
