I think you're absolutely right. We need a common set of labels (at least for core objects) and they need to have clear definitions.
Tom Cornilliac wrote:
Save was introduced for editors who were spending a long time editing the one object and having there session run out before they finish and therefore loosing all their changes. Save allows them to continue editing without having to finish the plp.\
I understand the reason and frankly I think it's great. My point was "Save" is (in my experience) an often misunderstood feature/label. Windows users have come to expect a certain behavior from buttons labeled "Save".
Are older clients who had no "SAVE" option understand implicitly what save means :) But again I agree it's a little ambiguous when it should be intuitive.
What I see is a pattern of initial confusion related to that little button. This leads me to conclude that there's room for improvement in the interface.
We've been looking at a host of standard PLP/Wizard UI improvements. I'd like to see a progress indicator -- eg. you are at step 3 of 5 (or a visual to that effect). I often wonder if the drop down is such a great idea -- perhaps an expanded set of buttons might be appropriate and so on.
At the very least we ought to have buttons for the following functions: - saving the state of the PLP without committing to the DB - Cancelling the PLP and clearing the PLP data - Completing the PLP - Next/Previous steps - A menu of items
Perhaps we ought to put fwd a few screenshots of potential interfaces?? Anyone got ideas?? Handy with Fireworks?
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
