CHI-WEB Archives

ACM SIGCHI WWW Human Factors (Open Discussion)

CHI-WEB@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"ACM SIGCHI WWW Human Factors (Open Discussion)" <[log in to unmask]>
Subject:
From:
Date:
Mon, 28 Nov 2005 12:36:14 -0500
Reply-To:
Parts/Attachments:
text/plain (32 lines)
Hello - I've searched the archives and didn't find anything on this topic.

We are revisiting standards for a custom workstation and the following
notion came up: Should developers/vendors be required to lock navigation
(or controls) in view so they don't scroll out of view?

Our users have multiple applications open across two monitors. Applications
are often delivering table-style data about a particular customer, product
etc. A few apps are keeping controls persistently in view by locking them
in a top pane (frame, etc.).

Do you have any experience in requiring apps to do this?

- True benefits for users?
- Difficulties for developers/vendors?
- Published research?

Note: as we move forward, we will likely be doing more and more web-based
apps.

Thanks!

Pat Malecek
[log in to unmask]

    --------------------------------------------------------------
    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
    --------------------------------------------------------------

ATOM RSS1 RSS2