[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-usability
Subject: Re: [KDE Usability] Review Request 108686: hidden items in context menu: usability question
From: Matěj_Laitl <matej () laitl ! cz>
Date: 2013-01-31 20:09:32
Message-ID: 20130131200932.3598.61913 () vidsolbach ! de
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/108686/
-----------------------------------------------------------
(Updated Jan. 31, 2013, 8:09 p.m.)
Review request for Amarok and KDE Usability.
Changes
-------
Add screenshot captions.
Description (updated)
-------
Some of the actions in context menu are shown only when the Shift key is pressed. We were \
wondering, if this were okay at all, and if yes, which hint would be better.
To explain a bit more:
in Amarok 2.5, the context menu (of a track, album etc.) used to have all the options (among \
others):
* Copy to Collection ->
* Move to Collection ->
* Move to Trash
* Delete
With goal to (a) make accidental data-loss (or unwanted effect) harder for novice users (b) \
make the context menu simpler, a fancy "hold Shift to swich to move/dangerous operations" \
behaviour was implemented:
- without Shift held:
* Copy to Collection -> [with "Press Shift key for ..." tooltip]
* Move to Trash [with "Press Shift key for ..." tooltip]
- with Shift key held (updates itself immediately after pressing the key):
* Move to Collection ->
* Delete
However, we discovered that discoverability (hehe) is really a problem when even experienced \
long-term Amarok users didn't know about the way to trigger Move/Delete. What would be the best \
approach here?
Diffs
-----
Diff: http://git.reviewboard.kde.org/r/108686/diff/
Testing
-------
File Attachments
----------------
Behaviour of Amaork 2.7 with Shift key held
http://git.reviewboard.kde.org/media/uploaded/files/2013/01/31/hidden_actions.png
Suggestion to improve discoverability
http://git.reviewboard.kde.org/media/uploaded/files/2013/01/31/hint_1.png
Behaviour of Amarok 2.7 without any key held
http://git.reviewboard.kde.org/media/uploaded/files/2013/01/31/hint_2.png
Thanks,
Edward Hades Toroshchin
[Attachment #5 (text/html)]
<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="http://git.reviewboard.kde.org/r/108686/">http://git.reviewboard.kde.org/r/108686/</a>
</td>
</tr>
</table>
<br />
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: \
url('http://git.reviewboard.kde.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); \
background-position: left top; background-repeat: repeat-x; border: 1px black solid;"> <tr>
<td>
<div>Review request for Amarok and KDE Usability.</div>
<div>By Edward Hades Toroshchin.</div>
<p style="color: grey;"><i>Updated Jan. 31, 2013, 8:09 p.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Changes</h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid \
#b8b5a0"> <tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; \
white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Add screenshot \
captions.</pre> </td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description (updated)</h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px \
solid #b8b5a0"> <tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; \
white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Some of the actions \
in context menu are shown only when the Shift key is pressed. We were wondering, if this were \
okay at all, and if yes, which hint would be better.
To explain a bit more:
in Amarok 2.5, the context menu (of a track, album etc.) used to have all the options (among \
others):
* Copy to Collection ->
* Move to Collection ->
* Move to Trash
* Delete
With goal to (a) make accidental data-loss (or unwanted effect) harder for novice users (b) \
make the context menu simpler, a fancy "hold Shift to swich to move/dangerous \
operations" behaviour was implemented:
- without Shift held:
* Copy to Collection -> [with "Press Shift key for ..." tooltip]
* Move to Trash [with "Press Shift key for ..." tooltip]
- with Shift key held (updates itself immediately after pressing the key):
* Move to Collection ->
* Delete
However, we discovered that discoverability (hehe) is really a problem when even experienced \
long-term Amarok users didn't know about the way to trigger Move/Delete. What would be the \
best approach here?</pre> </td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
</ul>
<p><a href="http://git.reviewboard.kde.org/r/108686/diff/" style="margin-left: 3em;">View \
Diff</a></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">File Attachments </h1>
<ul>
<li><a href="http://git.reviewboard.kde.org/media/uploaded/files/2013/01/31/hidden_actions.png">Behaviour \
of Amaork 2.7 with Shift key held</a></li>
<li><a href="http://git.reviewboard.kde.org/media/uploaded/files/2013/01/31/hint_1.png">Suggestion \
to improve discoverability</a></li>
<li><a href="http://git.reviewboard.kde.org/media/uploaded/files/2013/01/31/hint_2.png">Behaviour \
of Amarok 2.7 without any key held</a></li>
</ul>
</td>
</tr>
</table>
</div>
</body>
</html>
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic