<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I don't know. The current hover-to-open is very confusing to new
users. It is particularly annoying when the menu disappears while
you are trying <br>
to move the cursor to it. Using clicks makes opening the menu
persistent until another click rather than dependent on the cursor
position.<br>
<br>
I am still a fan of the original Sugar UI in which the primary
operation was to click on an icon. This also significantly reduces
the dependence on translation <br>
since young learners quickly remember the icons and what they are
for.<br>
<br>
If tooltips were used for the hover, the user could get the name of
an activity before clicking. This is one discrete piece of
information rather than a <br>
complex set of information.<br>
<br>
I think the Journal should be less integrated to the Home View. An
activity is a tool. Launching an activity is taking the tool from
the box. The Journal <br>
is where work-in-progress or completed-work is stored. The user
easily understands to start a new project, open in the Home View. To
resume a work-in-progress, click on the object in the Journal. The
'save as' and 'screenshot' features help by having the user name the
project so it can be quickly found <br>
in the Journal.<br>
<br>
Currently, it is very helpful that the icon of the activity which
will be launched from the Journal is shown. If it is correct the
user has only to click on the icon.<br>
If a different activity is needed (e.g. a screenshot to be modified
in Paint), the user right-clicks on the icon and selects the paint
activity. <br>
<br>
The buttons in Google and Firefox essentially take up as much of the
screen as desired. This gives the freedom to show larger icons and
use larger <br>
fonts. <br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 05/28/2016 02:18 PM, Sam Parkinson
wrote:<br>
</div>
<blockquote cite="mid:1464437896.1601.0@smtp.gmail.com" type="cite">Hi
Tony,<br>
<br>
On Thu, May 26, 2016 at 8:58 PM, Tony Anderson
<a class="moz-txt-link-rfc2396E" href="mailto:tony_anderson@usa.net"><tony_anderson@usa.net></a> wrote:<br>
<blockquote type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
Hi Sam<br>
<br>
I like the Google apps button on the Google main page and the
menu button at the far right of the Firefox toolbar. They show
as a popup and have <br>
plenty of screen space for icons and larger font sizes. This
could support a design in which a left-click always causes an
action and a right-click is required <br>
to open up the 'palette' This is done well on the standard
toolbar. <br>
<br>
On the Home View, for instance. I would prefer that
left-clicking on the icon launches the activity (new start). The
tooltip shows the name of the activity (and nothing else). A
right-click can open a list of instances available to be
resumed. Using the Google or Firefox style, the list of
instances can look exactly like the corresponding entry in the
Journal.</blockquote>
<div><br>
</div>
<div>I think that if we make palettes right click only, we loose
an important discoverability aspect. Do you find the
hover-to-open helpful or harmful to discoverability in your
experience?</div>
<div><br>
</div>
<div>I also think that the homeview palettes are a special case.
We aren't going to be able to add more items or elaberation to
the running activity palettes, or the buddy palettes. If we
wanted to make the journal more intergrated with the homeview,
couldn't we just replace the homeview with an enhanced journal?
(Did we discuss this on list? [1])</div>
<div><br>
</div>
<div>I find the idea of a larger font size interesting. Is the
current palette font size too small? It is also important to
remember that any font size increase makes the distance you need
to move the mouse bigger, which could be a negative.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sam</div>
<div><br>
</div>
<div>[1] <a moz-do-not-send="true"
href="https://www.sam.today/blog/sugar-nohomeview-design.html">https://www.sam.today/blog/sugar-nohomeview-design.html</a></div>
<br>
<blockquote type="cite"><br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 05/26/2016 12:44 PM, <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:sam@sam.today"><a class="moz-txt-link-abbreviated" href="mailto:sam@sam.today">sam@sam.today</a></a> wrote:<br>
</div>
<blockquote cite="mid:1464259460.1607.1@smtp.gmail.com"
type="cite">
<div>Hi All,</div>
<div><br>
</div>
<div>A while ago, I dropped a mention on the list to how many
users found the palette system confusing, at least in my
usability testing experiment.</div>
<div><br>
</div>
<div>I recently wrote this up, with a more detailed rational;
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://www.sam.today/blog/sugar-with-instant-palettes/">https://www.sam.today/blog/sugar-with-instant-palettes/</a></div>
<div><br>
</div>
<div>I invite you to comment on this. This could be an
interesting change for sugar (0.)110.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sam</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>