Comment 13 for bug 1103426
Revision history for this message
| Bogdan Stanciu (bstanciu) wrote Re: [Bug 1103426] Re: [Trunk/7.0] Naming issue on cancel button of project issue | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
While these words are fun for a brainstorming session (I liked void, I
would certainly not know what to do with it...), they do not add clarity
in a real life situation. We need usual wording, used everywhere, no
user is dedicated to Openerp only.
Cancel means close without saving almost everywhere. like save | cancel,
or Save | close, there is also OK |Cancel, but mostly in a dialogue.
I think that the "faulty" action is "set object to Cancelled status";
this shall be addressed. Why not just use something like I just wrote:
Set [object] to cancelled state/status
I would also avoid "close" and "cancel" put together as they are still
confusing.
thank you,
Bogdan
On 25. 01. 13 12:36, Daniel Reis (SECURITAS SA) wrote:
> "Invalidate" sounds excellent. Another possibility might be
> "Inactivate".
>
> Another suggestion is to place it's button on the far right, after the `statusbar`widget.
> That shouldn't be difficult, but right now the statusbar CSS forces it to be the right-most element, so that buttons after it are presented in the next line.
>