So one more comment which I'd like to clarify.
*The ideal proposal*
The *ideal* experience is when the user is in the middle of filling
out the event details and decide to move the lozenge to a different
time, the UI should be able to accommodate and temporarily preserve
the user's data in the form element.
Q. Is this only done by auto save or is there another way to
*temporarily* preserve the data when the user decides to move an
event lozenge half way through editing/filling out the form element
in the detail view?
If this is not possible by 0.7, then an alternate proposal is to not
allow users to make any modifications to the web UI until they have
finished filling out the forms in the detail view.
As discussed, if the user simply clicks out of the detail view when
they are in the middle of the filling out the form, an error dialog
will appear and display a message:
Save changes?
[Cancel] [Ignore] [Save]
On Apr 17, 2007, at 11:29 AM, Matthew Eernisse wrote:
1. Save the changes to the server.
2. Ignore the changes and change the contents of the form to the
new selection.
3. Cancel the action and return back to the form to verify what the
changes are before deciding whether or not to save.
As you can see, I'm not in favor of lots of text on the buttons, not
to mention too much text on error dialogs. Are people feeling
particularly strong about having to display 'Save Changes', 'Ignore
Changes' etc.?
Keep in mind, this is temporary and in the end our goal is to meet
the *ideal* proposal.
Thanks, -Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
