Bug 42892 - [Misc] unclear tooltips when workflow commands are inactive
Summary: [Misc] unclear tooltips when workflow commands are inactive
Status: NEW
Alias: None
Product: Lenya
Classification: Unclassified
Component: Miscellaneous (show other bugs)
Version: 2.0
Hardware: Other other
: P2 normal
Target Milestone: 2.0.1
Assignee: Lenya Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-13 08:49 UTC by michael.trindler
Modified: 2008-01-03 14:58 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description michael.trindler 2007-07-13 08:49:08 UTC
situation: doc 1 is submitted and therefore not editable; the edit commands are
not active (ok), the tooltip message to these commands should say something like
"document is not editable since in state review". The actual tooltips are not
helpful ("What You See Is What You Get" or "The event edit is not executable on
document ...").
Comment 1 Thorsten Scherler 2007-07-16 01:58:38 UTC
Renaming Lenya 1.4 to 2.0
Comment 2 Andreas Hartmann 2007-07-16 08:25:30 UTC
(In reply to comment #0)
> situation: doc 1 is submitted and therefore not editable; the edit commands are
> not active (ok), the tooltip message to these commands should say something like
> "document is not editable since in state review". The actual tooltips are not
> helpful (

> "What You See Is What You Get" or

That's an <acronym> element for WYSIWYG. Should we remove it?

> "The event edit is not executable on document ...").

Any ideas about an algorithm to generate a more comprehensible error message?
Comment 3 Andreas Hartmann 2007-07-17 04:08:07 UTC
(In reply to comment #2)

> Any ideas about an algorithm to generate a more comprehensible error message?

I'm afraid that's not trivial. Can we postpone this bug to 2.0.1?
Comment 4 J 2007-10-29 10:17:59 UTC
fine for me. additionally, tooltips must be shortened, because not all browsers
display them entirely. useful maximum should be about 50 chars.
Comment 5 Andreas Hartmann 2008-01-03 13:35:31 UTC
How about

  "You cannot {event} this document."

That's short and works in English, assuming that the event name is a verb.

If we provide i18n for event names, we can extend it to other languages:

  "Sie können das Dokument nicht {event}".
Comment 6 J 2008-01-03 14:50:26 UTC
sounds good. if it doesn't work in a particular language, we can always use "you
cannot invoke workflow event {event}" instead.
Comment 7 Andreas Hartmann 2008-01-03 14:58:16 UTC
(In reply to comment #5)
> How about
> 
>   "You cannot {event} this document."

The problem here is that the message doesn't tell why the document can't be
published (workflow/permissions/...). Can we live with this?