>
>
> (b) sending a paginated set at first, and allowing to select a full
> scrollable set


I recently visited some users who use an application that has default
setting 25 rows per page. I noticed that the first thing that users did when
they arrived at that page was to reset the page to Max. They use this
application this everyday. They complained why the system couldn't remember
their setting. That table usually has 100-250 rows.

There are two reasons why the user wants to see the entire list:

1. When the user knows the item is closer to the bottom of the table, it is
faster to find it by scrolling the entire table instead of clicking through
the pages. The user does not know which page the item might be in so the
user has to click through most of the pages.
2. The user wants to quickly compare two rows. It is fasters to scroll the
page up and down for the comparison. The user can filter the table for that
purpose also but an experienced user just needs to scan the data.

Our conclusion is that we need to build a table component that can list all
the data.

- Cindy

    --------------------------------------------------------------
           Tip of the Day: Postings must be in plain text
     CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[log in to unmask]
              MODERATORS: mailto:[log in to unmask]
       SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
    --------------------------------------------------------------