From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Kay Sievers <kay@vrfy.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Takashi Iwai <tiwai@suse.de>, Jens Axboe <axboe@kernel.dk>,
Oliver Neukum <oneukum@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to fix CDROM/DVD eject mess?
Date: Tue, 3 Feb 2015 13:34:32 +0000 [thread overview]
Message-ID: <20150203133432.05f0bb0e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <CAPXgP124AvjVp7-7g4Te7L9Pznppr-8XDHvHDpLy7mq6-vBCDA@mail.gmail.com>
> By working with people who spent a lot of time with the questions what
> the default behavior of user interfaces should be. Buttons, especially
> physical ones, need to give immediate feedback to the user. If they
> don't give it it, people will look for something else to get what they
> want.
So spend a day in a location which isn't full of desktop users. In an
environment where these are systems doing real world work you do not want
to be having CD-ROMs eject because someone pushed the wrong button or
because they bumped one.
Locked media has its place. Your argument about feedback btw sounds rather
like you've not thought it through. Users do want immediate feedback, but
sticking a box on the UI that says "XYZ is currently using the CD-ROM,
eject anyway" is immediate feedback too. Especially when XYZ is things
like "The machine cutting tool" or "The telephone hold music system"
Alan
next prev parent reply other threads:[~2015-02-03 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 13:20 Takashi Iwai
2015-02-02 19:03 ` Kay Sievers
2015-02-02 19:34 ` Maciej W. Rozycki
2015-02-02 19:45 ` Kay Sievers
2015-02-02 21:12 ` Maciej W. Rozycki
2015-02-03 12:36 ` Takashi Iwai
2015-02-03 8:52 ` Oliver Neukum
2015-02-03 13:34 ` One Thousand Gnomes [this message]
2015-02-03 17:53 ` Theodore Ts'o
2015-02-02 20:02 ` Austin S Hemmelgarn
2015-02-02 20:53 ` Ondrej Zary
2015-02-03 12:31 ` Takashi Iwai
2015-02-03 13:39 ` One Thousand Gnomes
2015-02-03 13:49 ` Takashi Iwai
2015-02-03 13:40 ` Austin S Hemmelgarn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150203133432.05f0bb0e@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=axboe@kernel.dk \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=oneukum@suse.de \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®