On Tue, 2009-02-03 at 16:43 +0100, Andreas Bartel wrote:
> Hello members,
>
> here is a link to a well elaborated article about usability in open
> source software.
Good article.
However, before we go off and try to improve an application with user
interface engineering, we should first properly document the existing
application via a manual that anyone can read. Thats user interface
engineering also, in a fashion, is user interface engineering intended for the
brain
Much of what's available now has little or no documentation worth
reading. It's left to experienced end users to "figure it out" on their
own. I've written software professionally for 30 years, and I can
"figure it out" on my own in most instances, but most end users can't.
They need a well written users manual that provides enough detail to
answer most questions. I'd like one too, so I wouldn't have to waste my
time "figuring it out".
The help system and documentation for Open Office is a prime example of
having a fairly good application with lousy documentation. If you want
to know how any function really works you have to write test code and
"figure it out" yourself. The documentation is too vague, and lacks real
world examples.
Even the books written about programming for Open Office approach the
subject matter from an altitude of 30,000 feet. "OpenOffice.org Macros
Explained" is a case in point. I bought it and its an OK book as far as
it goes, but that book should be part of the documentation for the
application, not an add on after the fact. It also doesn't cover the
subject matter well enough to allow me to say its a "GOOD" reference,
its mediocre at best.
User interface design is something to be looked at, but first lets have
the people that know the application best, the developers, also produce
some documentation for it that goes more than skin deep.
--
Bill Gradwohl
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
