On Apr 23, 2007, at 7:21 PM, Mimi Yin wrote:
My guess is that most of the time, users will instinctively click
Save without thinking too hard about it.
That is the goal for about 98% of the time because there is no
temporary save in the detail view–the desired behavior is to
implement some temporary save when a user is middle of filling out
the detail view.
This is most likely a common use case and an error dialog will soon
become tiresome for the user. Users benefit from a solution for
either auto save or some temporary save, as it allows the user to
edit a single event in both the detail and calendar view.
Either way, I don't feel particularly strongly about this issue. My
guess is that most of the time, users will instinctively click Save
without thinking too hard about it. The only time there might be
confusion is if the user finds themselves negotiating between
Cancel and Ignore.
If people don't feel strongly about the proposed buttons, then let's
finalize a decision on this proposal.
---
Save changes?
[Cancel] [Ignore] [Save]
If we were to replace 'Ignore' with 'Discard', is that more
descriptive to inform users that their changes/edits will be
discarded/thrown away?
I realize users may find some confusion in 'Cancel' and 'Ignore', but
I'm not convinced that labeling the buttons with 'Cancel Changes/
Edits', 'Ignore Changes/Edits', and 'Save Changes/Edits' are really
more descriptive about what will happen when the user selects them.
In the end, this will be a learning curve once the user makes a
selection for the first time. Eventually if the desired goal is to
eliminate the error dialog all together, that will help alleviate the
ambiguity in the buttons.
-Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
