Breadcrumbs in Kickoff
Martin Klapetek
martin.klapetek at gmail.com
Wed Dec 21 20:33:52 UTC 2011
On Wed, Dec 21, 2011 at 21:07, Alexey Chernov <4ernov at gmail.com> wrote:
> On 20 дек 2011 19:31:06 Rick Stockton wrote:
> > Alexey, you have two of KDE's smartest people (Aaron and Martin) in
> > agreement that we probably want to provide this via the "Back" Button on
> > the Mouse. (Less new code, less confusion, less maintenance headache.)
> > That's the option on the table, with tentative "+1" assessments. Would
> > that alternative be INADEQUATE, in a REALLY IMPORTANT way?
> >
> > If it's got a defect, I really don't see it. Please advise.
>
> No, nothing against except that mouse buttons can be easily rearranged (for
> instance, I have 'back' and 'forward' buttons on my mouse but arranged
> them as
> 'copy' and 'paste'). Anyway it's definitely better to have it if it's easy
> to
> implement as you describe, so thank you for a good idea.
>
> In my opinion, the main discussion here is around GUI elements and this
> approach is quite similar to hotkeys, it's a little bit different story.
>
To play the devil's advocate here - as the main reason against bringing it
back is mostly the increased code complexity, then if you add whole support
for additional mouse buttons that actually trigger the back action, isn't
the back button then just like 10 lines of qml code? Ie. just hook the
onClick: to the "one-level-back" action?
But then again - I don't really care that much about that button as I use
mostly KRunner and I respect the decision. Should there be a vote though,
I'd probably vote in favor of it.
--
Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20111221/f679dc27/attachment.html>
More information about the Plasma-devel
mailing list