Differences between revisions 3 and 4
Revision 3 as of 2009-05-18 09:20:28
Size: 1023
Editor: dave@davidhbrown
Comment:
Revision 4 as of 2009-05-18 09:21:06
Size: 1084
Editor: dave@davidhbrown
Comment: Migrated to Confluence 4.0
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
#pragma page-filename DEV/versions/8683531
If where you write, "Main menu options will be ordered by usage frequency" you mean dynamic reorganization, I am concerned.  I have found Microsoft's and Adobe's efforts to "streamline" their menus by hiding things that haven't been used recently and moving items to the top just after I get used to finding them elsewhere around to slow me down more often than it helps.
#pragma page-filename DEV/versions/8683525
If where you write, "Main menu options will be ordered by usage frequency" you mean dynamic reorganization, I am concerned.  I have found Microsoft's and Adobe's efforts to "streamline" their menus by hiding things that haven't been used recently and moving items to the top just after I get used to finding them elsewhere around to slow me down more often than it helps.
Line 6: Line 6:
Adding a short "frequent tasks" list \--(\)-- sort of like recently used files in Office would be useful, but I would suggest that it should be distinct from the main navigation structure. There is a real risk that dynamic reorganization will actually hinder users by frustrating them when features they're still learning move around. Adding a short "frequent tasks" list -- sort of like recently used files in Office would be useful, but I would suggest that it should be distinct from the main navigation structure. There is a real risk that dynamic reorganization will actually hinder users by frustrating them when features they're still learning move around. Dynamic menus definitely do not make me feel more secure in what I do.

If where you write, "Main menu options will be ordered by usage frequency" you mean dynamic reorganization, I am concerned.  I have found Microsoft's and Adobe's efforts to "streamline" their menus by hiding things that haven't been used recently and moving items to the top just after I get used to finding them elsewhere around to slow me down more often than it helps.

Adding a short "frequent tasks" list -- sort of like recently used files in Office would be useful, but I would suggest that it should be distinct from the main navigation structure. There is a real risk that dynamic reorganization will actually hinder users by frustrating them when features they're still learning move around. Dynamic menus definitely do not make me feel more secure in what I do.

(Unimportant: Is there a special meaning for "wizzard" with two "z"s instead of the usual one? I tried Googling and found a couple references to musicians...)

MailmanWiki: DEV/global requirements/0000 (last edited 2009-05-18 09:21:06 by dave@davidhbrown)