Hi All,<div><br></div><div>I have made a patch to implement this proposal: <a href="https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/326">https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/326</a></div><div><br></div><div>You really should try it out. It is surprising how much quicker it makes Sugar feel. Sugar feels much more snappy.</div><div><br></div><div>It probably might even Sugar feel snappier on the XO1s, given that it isn't draining any more cpu cycles. In fact, it probably uses less CPU given it removes some code and "animations", but that is so marginal</div><div><br></div><div>Thanks,</div><div>Sam<br><br>On Sat, May 28, 2016 at 11:50 PM, Walter Bender <walter.bender@gmail.com> wrote:<br>
<blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 28, 2016 at 9:22 AM, Tony Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Walter,<br>
<br>
I am not sure why the right-click should not open a palette whose
function is comparable to the context-menus in other systems. I
don't know how a <br>
right click is used as an accelerator.<br></div></blockquote><div><br></div><div>It is accelerating what hover does.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<br>
The issue is that a right-click can open a palette which stays open
until there is another click or the user clicks in the palette. This
is much better than our current disappearing menus (if you move the
cursor so as to leave the boundary of the icon and its palette for a
microsecond, it disappears and you have to start over. This also
means hover can be used for tooltips - a single piece of information
(the name of the activity, for example.<br></div></blockquote><div><br></div><div>We have more info the longer you hover. We could perhaps delay the disappearance or expand the hit area to address your concern. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<br>
I think Sam's concerns about the home view arises from its being
used to resume activities which is redundant to the use of the
Journal view for that purpose.<br>
Originally in Sugar, a click on the icon launched an activity (as it
does now in the List View. A click on an icon in the Journal view
resumed the activity. This <br>
was a very simple and understandable interface. In most cases users
did not have to see or understand a palette menu.<br>
<br></div></blockquote><div><br></div><div>We went through this many times. The current behavior reflects the need to address among other things, journal spam. In my computing life, 90+% of the time I am continuing existing work rather than starting something new. And we have a keyboard shortcut for the latter behavior. We did discuss having some activities be able to override the default behavior. Which would you suggest?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
Actually this style probably promotes discoverability. When a user
clicks on an icon in the Home View and an arbitrary activity
instance is launched, the <br>
user does not have a predicable starting point. This is particularly
difficult in situations where an XO is shared among multiple users
since Sugar has no <br>
way to know who was the last to launch an activity.</div></blockquote><div><br></div><div>We need to address the multiple user issue separately. Each user should have their own history. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class="HOEnZb"><font color="#888888"><br>
<br>
Tony</font></span><div><div class="h5"><br>
<br>
<br>
<br>
<div>On 05/28/2016 02:29 PM, Walter Bender
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, May 28, 2016 at 8:18 AM, Sam
Parkinson <span dir="ltr"><<a href="mailto:sam.parkinson3@gmail.com" target="_blank">sam.parkinson3@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Tony,<span><br>
<br>
On Thu, May 26, 2016 at 8:58 PM, Tony Anderson <<a href="mailto:tony_anderson@usa.net" target="_blank"></a><a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>>
wrote:<br>
<blockquote type="cite"> 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>
</span>
<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>
</blockquote>
<div><br>
</div>
<div>+1. I implore you not to make any aspect of the
interface depend upon right click. It should always be an
accelerator, but nothing more. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<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>
</blockquote>
<div><br>
</div>
<div>I think a lot could be done in that space. Love to see
some concrete proposals. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<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 href="https://www.sam.today/blog/sugar-nohomeview-design.html" target="_blank">https://www.sam.today/blog/sugar-nohomeview-design.html</a></div>
<div>
<div><br>
<blockquote type="cite"><br>
<br>
Tony<br>
<br>
<div>On 05/26/2016 12:44 PM, <a href="mailto:sam@sam.today" target="_blank"></a><a href="mailto:sam@sam.today" target="_blank">sam@sam.today</a>
wrote:<br>
</div>
<blockquote 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 href="https://www.sam.today/blog/sugar-with-instant-palettes/" target="_blank">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></fieldset>
<br>
<pre>_______________________________________________
Sugar-devel mailing list
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</blockquote>
</div>
</div>
<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div data-smartmail="gmail_signature">
<div dir="ltr">
<div><font><font>Walter Bender</font></font><br>
<font><font>Sugar Labs</font></font></div>
<div><font><a href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br>
<br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Sugar-devel mailing list
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font><font>Walter Bender</font></font><br><font><font>Sugar Labs</font></font></div><div><font><a href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br><a href="http://www.sugarlabs.org" target="_blank"><font></font></a><br></div></div></div>
</div></div>
</blockquote></div>