Ticket #243 (closed Enhancement: fixed)
Remove the Save button
| Reported by: | jri | Owned by: | jri |
|---|---|---|---|
| Priority: | Major | Milestone: | Release 4.1 |
| Component: | DeepaMehta Standard Distribution | Version: | 4.0.10 |
| Keywords: | Cc: | Malte, silke, irau, JuergeN | |
| Complexity: | 5 | Area: | GUI / Usability |
| Module: |
Description
Saving should be implicit (like in DM2).
From the usability view it is very bad to have "Save" in the user's conceptual model. "Save" is a very unnatural operation. The user should not care about saving. Its up to the machine to ensure things are not lost.
Change History
comment:3 Changed 12 years ago by jri
- Status changed from accepted to closed
- Resolution set to fixed
The user must no longer care about saving.
DM ensures nothing is lost, e.g. when the user selects another topic while being in edit mode.
The "Save" and "Cancel" buttons are replaced by an "OK" button.
The "OK" button just allows the user to say "I'm done with editing". There is no need to press it.
Technically, DM initiates saving at these events:
- A topic or association is selected on the canvas
- A search is initiated
- A toolbar menu is opened
- The canvas's context menu is opened
- The OK button is pressed
comment:4 Changed 12 years ago by Jörg Richter
Webclient: saving is implicit (#243).
The user must no longer care about saving.
DM ensures nothing is lost, e.g. when the user selects another topic while being in edit mode.
The "Save" and "Cancel" buttons are replaced by an "OK" button.
The "OK" button just allows the user to say "I'm done with editing". There is no need to press it.
Technically, DM initiates saving at these events:
- A topic or association is selected on the canvas
- A search is initiated
- A toolbar menu is opened
- The canvas's context menu is opened
- The OK button is pressed
Close ticket 243.
