Mime-Version: |
1.0 |
Sender: |
|
X-To: |
|
Date: |
Fri, 11 Mar 2005 13:20:45 -0500 |
Reply-To: |
|
Subject: |
|
From: |
|
In-Reply-To: |
|
Content-Type: |
text/plain; charset="us-ascii"; format=flowed |
Parts/Attachments: |
|
|
I've thought about it a lot, too.
While there are certainly differences between Web and desktop apps, the
differences are fading. Some applications are in Web browsers because
that's what makes it easy for the client and the server to communicate.
They might be better off in a browser window without all the browser
toolbars and menus, but that's a different discussion. (I ran a CHI
workshop in about 1996 or something on the topic of Web apps, discussing
this sort of thing. I'd love to have another discussion like that, if I
ever went to CHI again.)
I try to get clients to build menu bars because there's just too much stuff
on the page and it has to be organized. The Windows & Mac menu standard is
File/Edit/View/.../Window/Help. That may not apply on the Web for a variety
of reasons (we don't have the same need for a File menu, for example).
BUT -- The thing about menus is that they serve as an organizing principle.
That's what we need. It's no longer enough to arrange buttons and links in
groups. There's just too much stuff to put on the page. To do it right, we
may need to have some sort of standard, the way there is on the desktop.
-- hs
At 03:26 PM 3/4/2005 -0500, Hagan Rivers wrote:
>Cindy --
>
>A great topic - one I've given a lot of thought to. Here's some things to
>consider:
- - - - - - - - - - - - - - - - - -
Hal Shubin, Interaction Design, Inc.
617 489 6595
www.user.com
--------------------------------------------------------------
Tip of the Day: Suspend your subscription if using auto replies
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
--------------------------------------------------------------
|
|
|