From kde-usability  Fri May 07 08:23:49 2010
From: Hans Chen <hanswchen () gmail ! com>
Date: Fri, 07 May 2010 08:23:49 +0000
To: kde-usability
Subject: Re: [KDE Usability] Users cannot find where to "safely remove" USB
Message-Id: <y2pc59230381005070123ia10e2f1bw5d06bac3c31a7b9c () mail ! gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-usability&m=127322066509685
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============0122777318=="

--===============0122777318==
Content-Type: multipart/alternative; boundary=001485f427725c95420485fcc7ee

--001485f427725c95420485fcc7ee
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I'm sorry for bringing this up again, but I skimmed through the posts (there
are quite many) and did a search for 'context' but still couldn't find any
convincing arguments against it. I would appreciate if someone could fill me
in with what I've missed.

Against context menu:
- Clutter / Duplication of features
- Doesn't work on touch devices
- Some examples, such as iTunes, don't have a context menu for unmounting
devices
- If the unmount button was shown all the time, it wouldn't be a problem

Personally I'm in favor for adding a context menu. First of all, it would be
more consistent with Dolphin - or do some of you propose that the context
menu should be removed from Dolphin if it gets an "eject" button?

I don't believe that it adds unnecessary clutter. As others have noted,
there are already many irrelevant items in the context menu (such as Unlock
Widgets). Of course this doesn't justify adding another irrelevant one, but
in my opinion duplicating an action isn't necessary bad - this is seen in
other parts of Plasma. For example, consider an unlocked panel. You can
access the panel toolbox by clicking on the "cashew", but you can also right
click on the panel -> Panel Options -> Panel Settings. As another Plasma
example, you'll find "Unlock Widgets" in the Tool Box but also (often) when
right clicking on the desktop or panel.

I agree that we should keep other devices in mind, but that doesn't mean
that we have to limit ourselves to them. I'm not used to touch devices so I
won't discuss how to make it clearer in that case, but the suggestion to
always show the eject button sounds good in theory.

Now, adding a context menu item has an added benefit in my opinion - it
could show a disabled item with the text "Device can be safely removed" or
something similar when a device isn't mounted. From my limited experience
(family members and a few friends), some persons (a majority in my case)
don't realize that they can remove the device if the eject button isn't
shown and start looking for a "safely remove" option.

As a funny sidenote, and absolutely not used as an argument, I've never seen
a Windows user unmount a device from iTunes - they always go to the "safely
remove device" thingy in the system tray.

With best regards,
Hans Chen

On Thu, May 6, 2010 at 17:02, Dotan Cohen <dotancohen@gmail.com> wrote:

> Alright, it took some time but I showed the mockup to six users, and
> all agreed that they would now be able to find the eject buttons! Here
> is the bug, please comment on it:
>
> https://bugs.kde.org/show_bug.cgi?id=236586
>
> --
> Dotan Cohen
>
> http://bido.com
> http://what-is-what.com
> _______________________________________________
> kde-usability mailing list
> kde-usability@kde.org
> https://mail.kde.org/mailman/listinfo/kde-usability
>

--001485f427725c95420485fcc7ee
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,<br><br>I&#39;m sorry for bringing this up again, but I skimmed thro=
ugh the posts (there are quite many) and did a search for &#39;context&#39;=
 but still couldn&#39;t find any convincing arguments against it. I would a=
ppreciate if someone could fill me in with what I&#39;ve missed.<br>
<br>Against context menu:<br>- Clutter / Duplication of features<br>- Doesn=
&#39;t work on touch devices<br>- Some examples, such as iTunes, don&#39;t =
have a context menu for unmounting devices<br>- If the unmount button was s=
hown all the time, it wouldn&#39;t be a problem<br>
<br>Personally I&#39;m in favor for adding a context menu. First of all, it=
 would be more consistent with Dolphin - or do some of you propose that the=
 context menu should be removed from Dolphin if it gets an &quot;eject&quot=
; button?<br>
<br>I don&#39;t believe that it adds unnecessary clutter. As others have no=
ted, there are already many irrelevant items in the context menu (such as U=
nlock Widgets). Of course this doesn&#39;t justify adding another irrelevan=
t one, but in my opinion duplicating an action isn&#39;t necessary bad - th=
is is seen in other parts of Plasma. For example, consider an unlocked pane=
l. You can access the panel toolbox by clicking on the &quot;cashew&quot;, =
but you can also right click on the panel -&gt; Panel Options -&gt; Panel S=
ettings. As another Plasma example, you&#39;ll find &quot;Unlock Widgets&qu=
ot; in the Tool Box but also (often) when right clicking on the desktop or =
panel.<br>
<br>I agree that we should keep other devices in mind, but that doesn&#39;t=
 mean that we have to limit ourselves to them. I&#39;m not used to touch de=
vices so I won&#39;t discuss how to make it clearer in that case, but the s=
uggestion to always show the eject button sounds good in theory.<br>
<br>Now, adding a context menu item has an added benefit in my opinion - it=
 could show a disabled item with the text &quot;Device can be safely remove=
d&quot; or something similar when a device isn&#39;t mounted. From my limit=
ed experience (family members and a few friends), some persons (a majority =
in my case) don&#39;t realize that they can remove the device if the eject =
button isn&#39;t shown and start looking for a &quot;safely remove&quot; op=
tion. <br>
<br>As a funny sidenote, and absolutely not used as an argument, I&#39;ve n=
ever seen a Windows user unmount a device from iTunes - they always go to t=
he &quot;safely remove device&quot; thingy in the system tray.<br><br>With =
best regards,<br>
Hans Chen<br><br><div class=3D"gmail_quote">On Thu, May 6, 2010 at 17:02, D=
otan Cohen <span dir=3D"ltr">&lt;<a href=3D"mailto:dotancohen@gmail.com">do=
tancohen@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204,=
 204); padding-left: 1ex;">
Alright, it took some time but I showed the mockup to six users, and<br>
all agreed that they would now be able to find the eject buttons! Here<br>
is the bug, please comment on it:<br>
<br>
<a href=3D"https://bugs.kde.org/show_bug.cgi?id=3D236586" target=3D"_blank"=
>https://bugs.kde.org/show_bug.cgi?id=3D236586</a><br>
<div class=3D"im"><br>
--<br>
Dotan Cohen<br>
<br>
<a href=3D"http://bido.com" target=3D"_blank">http://bido.com</a><br>
<a href=3D"http://what-is-what.com" target=3D"_blank">http://what-is-what.c=
om</a><br>
</div><div><div></div><div class=3D"h5">___________________________________=
____________<br>
kde-usability mailing list<br>
<a href=3D"mailto:kde-usability@kde.org">kde-usability@kde.org</a><br>
<a href=3D"https://mail.kde.org/mailman/listinfo/kde-usability" target=3D"_=
blank">https://mail.kde.org/mailman/listinfo/kde-usability</a><br>
</div></div></blockquote></div><br>

--001485f427725c95420485fcc7ee--

--===============0122777318==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

--===============0122777318==--