[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: Breadcrumbs in Kickoff
From:       Xavier Sythe <me () sythe ! me>
Date:       2011-12-21 16:59:49
Message-ID: CANYhfZVZ3iqndkny9Z_arT098DW3DvFFnNXfgiVx7WLg5knUkQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Alexey made several valid points.

It's not a question of whether or not to "add" a back button, it's a
question of whether or not to restore it.

If it's a question of redundancy, one might argue that the new breadcrumb
navigation could be removed in favour of the classic back button.

After all, most of the sub-categories are less than one level deep.

As for the notion that most prominent KDE apps don't possess back buttons,
there are actually quite a few examples, such as Konqueror/Rekonq, the
"System Settings" application, and Dolphin.
Dolphin arguably also has redundancy, as it possesses both breadcrumb
navigation and a back button.

If both Aaron and Martin claim to want consistency, why are they going
against the paradigms implemented in Dolphin, namely BOTH the back button
and breadcrumb navigation.

"(Btw. don't even try to
rally now that users post to the bug report. If that is going to happen I
will
make sure that the bug gets made read only)."

Martin, how can you claim to care about the opinions of KDE's userbase,
when you refuse to consider the possiblity that many of KDE's users may
want this feature?

Why would you make it read-only if you care about the community's opinion?

You don't have any statistics invalidating my statements.

Have KDE users requested the removal of the back button?
No.

Have KDE users requested the reinstatement of the back button?
Yes.

Do we care about KDE's users?
Yes.

So, why are we removing a feature?  A feature that few, perhaps none of the
users have complained about.


The fact that any users made the effort to not only register to the issue
tracker, but also find the specific issue and post to it, demonstrates
that, in fact, more users want the back button, than those that would ask
for its removal.

In fact, it should be obvious that users care about the back button, given
that I, a mere user, have spent close to 2 months pursuing this issue, and,
consequently, have joined this mailing list.  In the past, have you
encountered such ire?  Such dedication to a single feature?

Regardless of whether the back button is reinstated, I will support adding
the mouse's back button as a way to go back.  The back button is a staple
of modern UI, featured prominently in all file/web browsers.


Xavier Sythe

[Attachment #5 (text/html)]

<div>Alexey made several valid points.</div><div><br></div><div>It&#39;s not a \
question of whether or not to &quot;add&quot; a back button, it&#39;s a question of \
whether or not to restore it.</div><div><br></div>If it&#39;s a question of \
redundancy, one might argue that the new breadcrumb navigation could be removed in \
favour of the classic back button.<div>

<br></div><div>After all, most of the sub-categories are less than one level \
deep.<br><div><br>As for the notion that most prominent KDE apps don&#39;t possess \
back buttons, there are actually quite a few examples, such as Konqueror/Rekonq, the \
&quot;System Settings&quot; application, and Dolphin.</div>

<div>Dolphin arguably also has redundancy, as it possesses both breadcrumb navigation \
and a back button.</div><div><br></div><div>If both Aaron and Martin claim to want \
consistency, why are they going against the paradigms implemented in Dolphin, namely \
BOTH the back button and breadcrumb navigation.</div>

<br><div>&quot;(Btw. don&#39;t even try to</div><div>rally now that users post to the \
bug report. If that is going to happen I will</div><div>make sure that the bug gets \
made read only).&quot;</div><div><br></div><div>Martin, how can you claim to care \
about the opinions of KDE&#39;s userbase, when you refuse to consider the possiblity \
that many of KDE&#39;s users may want this feature?</div>

<div><br></div><div>Why would you make it read-only if you care about the \
community&#39;s opinion?</div><div><br></div><div>You don&#39;t have any statistics \
invalidating my statements. </div><div><br></div><div>Have KDE users requested the \
removal of the back button?</div>

<div>No.</div><div><br></div><div>Have KDE users requested the reinstatement of the \
back button?</div><div>Yes.</div><div><br></div><div>Do we care about KDE&#39;s \
users?</div><div>Yes.</div><div><br></div><div>So, why are we removing a feature?  A \
feature that few, perhaps none of the users have complained about.</div>

<div><br></div><div><br></div><div>The fact that any users made the effort to not \
only register to the issue tracker, but also find the specific issue and post to it, \
demonstrates that, in fact, more users want the back button, than those that would \
ask for its removal.</div>

<div><br></div><div>In fact, it should be obvious that users care about the back \
button, given that I, a mere user, have spent close to 2 months pursuing this issue, \
and, consequently, have joined this mailing list.  In the past, have you encountered \
such ire?  Such dedication to a single feature?</div>

<div><br></div><div>Regardless of whether the back button is reinstated, I will \
support adding the mouse&#39;s back button as a way to go back.  The back button is a \
staple of modern UI, featured prominently in all file/web browsers.</div>

<font color="#999999"><br></font><div><font \
color="#999999"><br></font></div><div><font color="#999999">Xavier \
Sythe</font></div></div>



_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic