| Wording: unsaved changes [message #1431402] |
Thu, 25 September 2014 16:44 |
 Jeremie Bresson
Messages: 1252
Registered: October 2011 |
Senior Member |
|
|
I try to update the documentation about the notion of "unsaved changes" in scout.
"unsaved changes" seems to be used on the Mac OS X platform:
Mac OS X: Seeing if You Have Unsaved Changes
This is probably why I like it a lot.
The Eclispe Platform seems to use the word "dirty" (they speak from dirty marker in the editor).
In scout we have also the notion of "saveNeeded" that is more or less the same. Each field can also be "touched"
I do not want to change the API (eg the name of the methods). But in the documentation and in the javadoc, we need to use the same notion. I think that "unsaved changes" is a good one.
Any thoughts?
I see it as a part of the form lifecycle hanlding (for me lifecycle also include stuff like: loading and saving data [form handler], form state [loading, open, stored], ...)
[Updated on: Thu, 25 September 2014 16:49] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.02619 seconds
] 
Search
Help
Register
Login
Home
