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

List:       kde-usability
Subject:    Re: [KDE Usability] Users cannot find where to "safely remove" USB
From:       Jan-Christoph Borchardt <jan () inquata ! com>
Date:       2010-04-11 17:12:13
Message-ID: r2ie1a40fbe1004111012l8ba31847t1ef59a403767239f () mail ! gmail ! com
[Download RAW message or body]

On 11 April 2010 18:35, Dotan Cohen <dotancohen@gmail.com> wrote:
>>> No, USB was intended for connecting peripherals, not removable
>>> storage. The connectors are not even reliable for repeated plug/unplug
>>> cycles, that is why one must take care to pull _out_, not to shake
>>> back and forth.
>>>
>>
>> That is of no interest for the user. Nowadays USB is highly used for
>> removable storage, operating systems need to adapt to that. All the
>> time some system is not used for what it was intended; but it is used
>> because it serves a need.
>>
>
> I agree. My comments about "how to implement that" were not
> disagreement, rather, they were serious questions. Like I said, the
> machine should adapt to the user. Now come up with the technical
> implementation.
>

That is all well and I understand that questioning an idea for
feasibility is needed. But seeing that I am no programmer, I can not
provide an implementation. The possibility is obviously there because
(as I previously said) download managers are already able to do that
(somehow). Be it by packet switching or some other concept I am not
internally familiar with.

Peter Grasch already mentioned some techniques that could be utilized.
I forwarded this thread to Canonical's Ayatana Project mailing list
and to the GNOME usability mailing list as well. If I am not the
person who can directly implement it, I'll point it out to those who
can.

>
>>> I agree with you 100% here. The computer should adapt to the human,
>>> not the other way around.
>>>
>>
>> So true. But then why do you expect the following?
>>
>
> I expect that the user will know to operate a mouse, will understand
> the concept of a file, and will know to operate common widgets. I do
> not expect zero knowledge. The only computer that I have ever heard of
> that expects zero knowledge is the Microsoft Surface.
>
> As technology improves (in this case, software) that will be one less
> thing that the user will have to know.
>

What about the iPad? I don't know if you read the post  »Future Shock «
by Fraser Speirs – you (correction: everyone) should:
http://speirs.org/blog/2010/1/29/future-shock.html

Computer and system internals are not things everyone has to know
about just because they use it. I certainly do not care HOW everything
works, IF it works. I have written about some other points here:
http://docs.google.com/Doc?docid=0AS7lb99nBsK2ZGhyNnN3Y2ZfMTdoZDZmNHNncw
(this address is ironically the best example of tech-induced
obfuscation)

>
>>> I do expect that the user will at a minimum know to wait until the
>>> computer says "you can remove the device now", whether that be due to
>>> the computer's instigation (as is the idea under consideration) or due
>>> to the user asking (by using the "Remove Safely" mechanism).
>>>
>>
>> You can not expect that. When I want my device removed, I remove it.
>
> You are reckless or irresponsible. Why you want to go through the
> intersection, do you not wait for the traffic light to indicate that
> it is safe?
>

This analogy is pointless. Removing USB drives is neither about my
life nor about the lives of others.

My point: The implementation is already there, only in another form:
USB drive – your Computer
USB connection – Internet connection
your Computer – the Internet
the function we need – download manager

Someone who can code just has to use it for USB drives. I'd be
surprised if something that is possible to do with internet sources is
not possible with a simple USB drive.

This is similar to  »provide undo instead of asking to confirm every time «.
_______________________________________________
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]