Re: Guidelines for scrolling vs. paging, max. number of ele ments on screen

 We have found in developing LOTS of form-based systems lately that
keeping the pages "whole", thus requiring some scrolling, often has a
dramatic positive effect on performance.  By doing an "autoscroll" when
the user uses the Tab key to jump to the next field when the current
field is at the bottom of the visible screen minimizes the need to
actually touch the mouse and use the scrollbar.

Far more important than anything has been to represent the forms
onscreen in the same order and with the same groupings as they are used
to seeing on their paper forms.  Even when it makes the screen seem
cluttered, to the expert user it's more efficient.

That being said, this is our experience when taking forms straight to
the screen.  If we have the luxury of refining the workflow and
redesigning their work a bit, some changes can be made to entry order,
grouping, etc and it's more "acceptable".

Ralph Lord
Northrop Grumman
USA

    --------------------------------------------------------------
     POSTINGS (in plain text): [email protected]
           SUBSCRIPTION CHANGES:  http://lists.syntagm.co.uk
            (or send email to mailto:[email protected])
    --------------------------------------------------------------