>
>  The key question is how the users scan the data.
>
>
> If the data appears with the most likely candidates at the top, the user
> is likely to scan slowly. In cases like this, the dynamic loading and
> presentation of subsequent data in the live model can keep up.
>

If the user searches a specific item and it happens to be positioned above
screen fold, then the user does not have to scroll the table.
If the user scans items starting from the top and gratually move down, live
scroll will help.



>  If the user is going to grab the scroll bar to quickly get further into
> the data set, skipping the initial items without even scanning them, the
> live model will likely struggle. This would be a scenario where the user is
> jumping into the data set (say, starting at a specific letter further into
> the data,) and therefore not interested in the stuff that is initially
> loaded. In this case, you'd be better off offering an indexed approach to
> the data.
>

I agree.

However, the struggle we have is that the users' needs of doing tasks on
each table is different. For example,
1. Search for a specific item by browsing - then view detail, drill down or
take an action
2. Scan the table to identify the trend or pattern. May view detail on a
specific item during the process. If they do it every day, they want to do
it quickly

The challenges are:
How to meet all the needs, make the table component consistent and make sure
the system can respond quickly.

Thanks and appreciate your thoughts!

- Cindy

    --------------------------------------------------------------
    Tip of the Day: Quote only what you need from earlier postings
     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
    --------------------------------------------------------------