<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Martin, I have an idea- even though I never even looked at Kickoff.
(Before writing this, I SHOULD have looked - but I don't have time
right now.) It seems to me that all of the layout issues, and the
GUI focus issues, of doing a GUI "back button" can be avoided: Just
listen for a QMouseEvent with QMouseEvent::button() value of:<br>
'XButton1' == 'BackButton' == 'ExtraButton1', and execute "back!"
whenever the event occurs in valid context.<br>
<br>
The names 'BackButton and 'ExtraButton1' aren't defined until Qt5,
but 'XButton1' is already present in Qt 4.7 (and many earlier 4.x
Releases, as well). Implementing this, Xavier (and others) would be
able to buy and use a mouse with Thumb buttons, "back" and
"forward", and just whack the buttons. No mouse movements at all,
and no GUI issues for us. Am I am guilty of "old style" thinking, or
does this enhancement make sense to you?<br>
<br>
My feeling is like a famous statement, from one of the bad guys in a
famous 'Spaghetti Western': "GUI Buttons? We Don't need no stinkin'
GUI Buttons !!!"<br>
<br>
(Perform an action on the Button Event, but leave the GUI scheme as
is: using breadcrumbs exclusively) <br>
<br>
<br>
<br>
<br>
<br>
On 01/-10/-28163 11:59 AM, Xavier Sythe wrote:
<blockquote
cite="mid:%3CCANYhfZUGGqsXLtuAC_MnF1jjdwKmANEmFa0qApLLJX91+MgM7w@mail.gmail.com%3E"
type="cite">Actually, the breadcrumbs don't really need to be
removed.<br>
I merely see the need to reinstate the back button.<br>
"I personally do not see any need for the back button any more."<br>
<br>
It's mostly a user experience perspective.<br>
<br>
It's a simple fact that it requires less mouse movement, hence,
less time, to click the back button, then it does to move your
mouse to the top of the menu, and use the breadcrumbs. Why?
Because the back button extends all the way down the length of the
menu. Instead of having to move your mouse to the top of the
menu, then to the left, you can simply move it to the left and
click the button.<br>
<br>
<br>
"The<br>
breadcrumbs add high value to Kickoff. It makes navigation in a
folder like<br>
structure like the application menu more convenient and much more
consistant<br>
with other parts of KDE applications, e.g. Dolphin's..."<br>
<br>
Just like in Dolphin, this menu style would feature both
breadcrumb navigation, and a back button.<br>
<br>
Would you support removing the back button from Dolphin, in favour
of just breadcrumbs?<br>
I doubt that anyone would support that.<br>
<br>
I've chatted briefly with the KDE Usability Team, and they
actually seemed to agree with me.<br>
<br>
Well some users might stick to the breadcrumb navigation, the
majority of users from previous versions of KDE are accustomed to
the back button, and appreciate its use, both in Kickoff as well
as in Dolphin. Including both types of navigation will ensure
that nobody complains, and presumably, lead to a better overall
user experience.<br>
<br>
Thanks,<br clear="all">
<font color="#999999">Xavier Sythe</font>
<div><br>
</div>
<br>
<br>
<br>
<div class="gmail_quote">On Fri, Dec 16, 2011 at 2:12 PM, Martin
Gräßlin <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mgraesslin@kde.org">mgraesslin@kde.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thursday 08 December 2011 16:01:33 Xavier
Sythe wrote:<br>
> Nearly two months ago, I contacted him, and asked him
to reverse the<br>
> controversial commit.<br>
> He has yet to reply.<br>
</div>
Please understand that not each developer has the time to
answer personal<br>
requests. You state yourself that it is controversial. Just
imagine each user<br>
disliking the feature sending a mail to Kevin. That just
doesn't scale.<br>
<br>
Asking to revert the feature is to be honest non-constructive
criticism. Like<br>
all other decisions on the default user interface they are
done with care. The<br>
breadcrumbs add high value to Kickoff. It makes navigation in
a folder like<br>
structure like the application menu more convenient and much
more consistant<br>
with other parts of KDE applications, e.g. Dolphin's
breadcrumb navigation.<br>
<br>
Just because you (and others) dislike the new feature it does
not justify to<br>
revert the commit. There are also users liking the feature, so
how should we<br>
suit both groups? Now please don't state that we need an
option for that. This<br>
is not possible as the code gets too complex and too difficult
to maintain.<br>
<div class="im">><br>
> When I asked the #KDE IRC channel about this, I was
told to contact the<br>
> members of this mailing list, to see if I could get the
commit reversed.<br>
</div>
Reverting the commit is clearly not an option. But what would
you say about<br>
improving the breadcrumbs in Kickoff? Getting them into a
state that you want<br>
to use them and not the out-of-place back button?<br>
<br>
Have a look at my recent blog post [1] about the work on
Kickoff for 4.9. It<br>
is easy to give this version a try, it installs alongside the
existing<br>
Kickoff. I personally do not see any need for the back button
any more.<br>
<br>
Kind Regards<br>
Martin Gräßlin<br>
<br>
New Kickoff Maintainer after branch merged into master<br>
<br>
[1] <a moz-do-not-send="true"
href="http://blog.martin-graesslin.com/blog/2011/12/experience-from-porting-%0Akickoff-to-qml/"
target="_blank">http://blog.martin-graesslin.com/blog/2011/12/experience-from-porting-<br>
kickoff-to-qml/</a></blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>