Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!sun!imagen!atari!portal!cup.portal.com!MJB
From: MJB@cup.portal.com (Martin J Brown-Jr)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Standard File Requesters
Message-ID: <19070@cup.portal.com>
Date: 2 Jun 89 09:41:44 GMT
References: <1106.AA1106@amigash>
Distribution: usa
Organization: The Portal System (TM)
Lines: 39

There has been one very obvious design flaw that has, regrettably, shown up
in all/most windowing system file requesters. The flaw is separating the
scroll arrow gadgets, putting them at opposite ends of the slider gadget.

IMHO, this is just plain bad design.

First, it seems to me a user is going to use either the arrows or the slider,
in any one instance of useage. When the user grabs either one of the arrows,
then overshoots the mark he/she is going to want to correct the situation
by using the other arrow. And as we all know, the other arrow is just about
as far away as possible, at the opposite end of the requester. And if the
requester has been sized to max_height to show a lot of files, the user ends
up moving the mouse just about the max_distance to get from one arrow to the
other. DUMB DUMB DUMB DUMB!

(don't give me that "just use a mouse accelerator" crap either, I use one)

IMHO, the two arrows would be in the best position if they were toegether,
one just above the other. That way shifting from one to other couldn't be
easier or quicker, with little chance for the horizontal positional error
to occur over such a short distance (h error much easier to get when 
moving over longer distances). This short distance reduces the attention for
aiming that is needed.

The remaining question is whether to put the two arrows at the top or bottom
of the slider. Since 99% of the boolean gadgets that will be needed to be
used after selecting the file are at the bottom, it seems obvious to me that
the two arrows should be below the slider.

If the requester designer puts the arrows together below the slider, and
puts the next most likely bool gadget ("OK", "LOAD", etc.) below the arrows,
and the user scrolls his/her selection to the bottom of the scroll area,
next to the arrows, about 99% of the most common action ever to occur with
this requester will occur within about a radius of inch or two (ok 2.5",:->)
no matter how tall the requester gets.

This sure seems logical, ergonomical, and .`. the most proper way to incorpora
these arrow gadgets.
                                - MJB -