[Sigia-l] Pillars of Ergonomics

[Listera]

"Eric Reiss" wrote:

> Does this also apply to the fellow who's going to design the
> multi-function touch screen you just suggested? I think not.

One reason why many/all functions may not be consolidated into a single
screen is that if that screen fails (heck, it could be running Windows :-),
then the driver is in big trouble, bigger than if one of many instruments
fails. The other reason is that multiple instruments allow the driver to
*scan* multiple kinds of info simultaneously and everything is visible, but
like tabs and menus, a multi-function screen obscures what it's not
displaying at the moment. Unless you manage to cram all that info into a
single screen, then "visibility" is greatly reduced.

If David can explain what an IA/ID does *while* driving and survive, then
I'm sure he can defend what he said:-), but what he says about understanding
the language, structure, limits and possibilities of how you go about
designing and developing that screen still applies here. It may or may not
be HTML/CSS (and I don't see why that would be impossible or undesirable),
but it'll have to be some markup language.

It's about understanding the boundaries of your tools. You can empirically
observe this by putting a good print designer used to working with
traditional tools in front of a computer and ask him to design something
interactive.

Ziya
Nullius in Verba