In the application I'm presently working on, we take a similar approach to Andres "Atlassian", but present this message at the point of navigation away from form, without saving, (this is a fairly standard point to present the message). The message has typical actions "Return", "Discard/Cancel" "Save".
As Jack pointed out, saving data as the user enters it, is always a valuable feature. I differ with Jack in that a "Save" button can be a benefit in this case as well, as it reinforces to users that their data has been saved, (note this reinforcement is more important with non-repetitive, non-trivial data entry), (I'll caveat for experienced user's forcing a "Save" for no purpose does suck). Also given users may want to discard any entries, it would be kind of odd to have just "Undo" options. Thus a "Cancel" button - negative action becomes valuable, and should also have a corresponding positive action, such as "Save". We also have the case of different execution options of initial "Save" VS "Discard" and interim "Save" VS "Undo" VS "Discard". And lastly there's the interim "Save" VS "Submit", with "Submit" being an actual and necessary Finalization step, (leads to workflow, etc). -- Joseph Rich Rogan President UX/UI Inc. http://www.jrrogan.com ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
