On Mon, Aug 08, 2011 at 05:49:07PM +0200, Emanuel Rumpf wrote:
> Depending on existing knowledge, the amount of
I didn't do that. But a user who just quits if things are
not immediately obvious and who refuses to read documentation
because that's boring compared to clicking around is not
> Usability (better: user-friendlyness ) is about supporting the learning process.
One question is *which* existing knowledge, understanding or
learning process. The software itself or the application
domain ? It's IMHO not the task of a developer of audio
sofware to teach audio engineering, not even to make his
application usable for someone who doesn't have the
required background. And the expectation (common enough)
that you can learn any application domain by clicking
around in some software is just not realistic.
I have never seen a car that tries to teach you how to
drive, and learning this takes a lot more than using a
car's basic controls.
> About 12 years ago, I've been someone who did a hardware-reset,
It's a tool for people who know what they are doing, and you
have to read the manual or at least some introduction to
understand how it works. Why didn't you do that ? :-)
Linux-audio-user mailing list