Mimi Yin wrote:
But what if the web convention was a band-aid solution to make up for
a lack of desktop functionality? And now that we're able to implement
desktop functionality, do we still want the band-aid solution on top
of the real solution?
To illustrate my point: Do we want the keyboard interaction in Scooby
to be:
1. Use arrow keys to move focus between Event Lozenges (visualized via
the dotted outline) and then hit Enter to actually Select the Event; OR
2. Use arrow keys to move between Event Lozenges, thereby
Automatically Selecting the Events as you Navigate?
I agree that 2 makes much more sense- but you're talking about selection
and focus together... it should be possible to have an item selected in
the calendar canvas, but focus be in the detail view (in either product)
- and if you're in that state, if you have a dotted line around the
_selected_ item in the calendar, and a dotted line around a _focused _
widget, how does the user know what is focused - i.e. where keystrokes
will go? I think that is the crux of the issue here - if you adopt
something similar for focus and selection, its going to get confusing....
I think in Scooby, we should allow users to Navigate between Days of
the Week by just Selecting the Day of the Week, rather than having to
do the whole Focus + Enter thing. This kind of Auto-Selection is
exactly the kind of interaction that makes Desktop apps feel smooth.
I'm trying to understand what gesture is behind "just Selecting the Day
of the Week" - i.e. is this an arrow key? A tab? I'm not sure I see what
you're getting at....
Alec
Mimi
On May 2, 2006, at 4:16 PM, Jeremy Epstein wrote:
Thats not 100% true -- it is possible to suppress all conventional
focus indicators-- I believe yahoo does this on their new web mail
application.
But should you?
When you get to the point you are overriding all basic interactivity
you might have a "web-delivered" desktop application, but its no
longer a web app in any sense of the word. Which is really the heart
of the discussion-- If there is a conflict in behavior between web
convention and "chandler convention" which do you stick with? If you
expect the bulk of your users to come from chandler, and should those
users find comfort in chandlers quirks which is the bigger sin?
inconsistency with chandler, or inconsistency with web convention.
This happens all the time with desktop apps-- apple, microsoft,
macromedia, and adobe each maintained a separate and unique set of
key shortcuts. If you are writing an adobe app do you follow mac
convention? windows convention? your internal convention?
What key shortcut quits an app? ctrl-Q? ctrl-X? esc?
How does redo work? ctrl+ y? ctrl+shift+z?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
