<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello<br>
My recommendation would be to place this AppMenu as per industry
standards, but makes it "moveable".<br>
<br>
Still ok to test different AppMenu contents? <br>
<br>
AM<br>
<br>
<div class="moz-cite-prefix">On 29/09/2012 17:27, <a class="moz-txt-link-abbreviated" href="mailto:gneandr@web.de">gneandr@web.de</a>
wrote:<br>
</div>
<blockquote cite="mid:50671372.8050305@web.de" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 29.09.2012 15:35, Richard Marti
wrote:<br>
</div>
<blockquote cite="mid:5066F921.1060104@paenglab.ch" type="cite">
<pre wrap="">On 27.09.2012 17:39, Anne-Marie Bourcier wrote:
</pre>
<blockquote type="cite">
<pre wrap="">- Changing the aging UI is probably a wise move and can keep TB looking
"young" for a while,
- 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 :-) )...As long as we document somewhere that you can go back to
your good old Menu bar with a right click;
</pre>
</blockquote>
<pre wrap="">Initially the left menu part was for the everyday (or almost everyday)
used items and the right part for the not so often used items. Initially
I would put only the most important items in it (a Test Pilot study
would helped here) but then I was outvoted to put all menu items from
main menu in the AppMenu.
</pre>
<blockquote type="cite">
<pre wrap="">- 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
- BUT I don't think that the actual AppMenu content/structure is
appropriate... _from the perspective of a User_, it's very confusing and
not logical (but you can argue this is MY opinion and I accept your
comment here)
- By consequence, I suggest the following:
* we take the current AppMenu content and call it Test A
* we reshuffle the content of the AppMenu and call it Test B (I've
suggestions already)
And we (I with whoever wants to help) conduct 2 tests with 2 different
groups of guinea pigs.
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.
If none of the AppMenu gets a positive scoring, then we have to
decide what to do with this new UI proposal in TB17
Having briefly discussed the point with Blake, I understand it might not
be trivial but I think this is worth the pain.
</pre>
</blockquote>
<pre wrap="">As already noted, for TB 17 this is a little bit late, but maybe we
could adapt the menu for TB 17.1 (or how the intermediate release will
be named) or 24 according this tests.
Richard
</pre>
</blockquote>
<br>
Maybe a easy going UI change -- but I think an important change
for the user acceptance -- would be the the AppMenu placement.<br>
See <a moz-do-not-send="true"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=795602"><b>Bug 795602</b></a>
-<span id="summary_alias_container"> <span
id="short_desc_nonedit_display">"Appmenu" should permanently
appear on "tabs-toolbar"<br>
<br>
Günter<br>
</span></span> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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>