<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
reading through this email thread I don't resist in my quality of
"end-user", to add to the conversation. I've checked what's called
the Application Menu (btw why is this called Applications menu?) and
I'd like to share my thoughts on this:<br>
<br>
- Changing the aging UI is probably a wise move and can keep TB
looking "young" for a while,<br>
- replacing some of the current Menu bar content and place it under
the AppMenu button sounds appealing. (I'm personally completely
overwhelmed when I go through the current menus! remember I'm a
"user"... not a developer - ad I don't give a cent to the Caracter
Encoding, or Activity Manager <span class="moz-smiley-s1"><span>
:-) </span></span>)...As long as we document somewhere that you
can go back to your good old Menu bar with a right click;<br>
<br>
- In order to know if this AppMenu button is acceptable to a large
number of users, a test would be really useful as each of us has a
different view on the UI and the debate can last for few weeks<br>
- BUT I don't think that the actual AppMenu content/structure is
appropriate... <u>from the perspective of a User</u>, it's very
confusing and not logical (but you can argue this is MY opinion and
I accept your comment here)<br>
- By consequence, I suggest the following:<br>
<ul>
<li>we take the current AppMenu content and call it Test A</li>
<li>we reshuffle the content of the AppMenu and call it Test B
(I've suggestions already)<br>
</li>
</ul>
And we (I with whoever wants to help) conduct 2 tests with 2
different groups of guinea pigs. <br>
We check together it AppMenu A or AppMenu B gather more
approvals than the other and then we retest the winner against more
end-users.<br>
If none of the AppMenu gets a positive scoring, then we have to
decide what to do with this new UI proposal in TB17<br>
<br>
Having briefly discussed the point with Blake, I understand it might
not be trivial but I think this is worth the pain.<br>
<br>
Let me know,<br>
AM<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 17/09/2012 08:46, <a class="moz-txt-link-abbreviated" href="mailto:acelists@atlas.sk">acelists@atlas.sk</a>
wrote:<br>
</div>
<blockquote cite="mid:20120917084631.403E2F08@atlas.sk" type="cite">
<pre wrap="">______________________________________________________________
</pre>
<blockquote type="cite">
<pre wrap="">Od: "Kent James" <a class="moz-txt-link-rfc2396E" href="mailto:kent@caspia.com"><kent@caspia.com></a>
Komu: <a class="moz-txt-link-rfc2396E" href="mailto:tb-planning@mozilla.org"><tb-planning@mozilla.org></a>
Dátum: 17.09.2012 00:45
Predmet: Re: TB 17.0a2 -- UI consistency
On 9/15/2012 7:33 PM, Blake Winton wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 15-09-12 19:31 , <a class="moz-txt-link-abbreviated" href="mailto:gneandr@web.de">gneandr@web.de</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Starting with Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0
Thunderbird/17.0a2 (en-US)
I recognized some UI changes. Don't want to start another discussion
about the philosophy of that change, but I expected with this
"massive" UI change we get a "cleaned" menu structure. It's about
getting the exactly same menu at different places .. if it's
necessary to offer a functionality at different places.
Fe. look at the different occurrences of the "Print" menu:
1. on the 3pane message list -- you have "Print Preview" and "Print .."
2. on the message in a tab -- you have "Print Preview" and "Print .."
3. on the message in a tab with the pull down menu -- you have [Other
Actions] --> "Print .."
ad 3. NO Print Preview
Is there an intension to overhaul those inconsistencies with the next
major release? So should we have a look at it with the upcoming QA
section?
</pre>
</blockquote>
<pre wrap="">I would certainly like to see an overhauled menu for the next major
release, but whether or not it gets done depends entirely on the community
</pre>
</blockquote>
<pre wrap="">
What I don't see in the future plan is a management structure that is
capable of moving toward consistency, so my fear is that "the community"
changes will result in even more fragmentation.
</pre>
</blockquote>
<pre wrap="">
There is still some hope, see e.g. <a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=738194">https://bugzilla.mozilla.org/show_bug.cgi?id=738194</a> .
aceman
_______________________________________________
tb-planning mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Anne Marie Bourcier
Mozilla Thunderbird</pre>
</body>
</html>