Suggestion #27748
make flyout messages more consistent
| Status: | Needs Feedback | Start date: | 2011-06-28 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Tags: | ||||
| Votes: | 0 |
Description
e.g. some modules present the flyout error messages and infos in the top toolbar overlaying the backend
Other modules like the scheduler show them inline it would be nice, if this would be consistent.
Related issues
| related to Usability Team - Suggestion #27679: Drag and Drop sorting for images | Closed | 2011-06-24 |
History
Updated by Kay Strobach almost 2 years ago
- File 28-06-2011_17-49-35.png added
Updated by Jens Hoffmann almost 2 years ago
What is that here all about?
Flyouts are Flyouts and MSG are MSG.
What is inconsistent?
Why is it related to the image thing?
Updated by Kay Strobach almost 2 years ago
In the scheduler the message could also be a flashmessage (flyout), that's how it's done in the new extmgm as well.
Most Messages in the core don't need to be there for a long time (static).
Otherwise the problem with the field should be shown like it is done in tceforms ;)
Updated by Jens Hoffmann almost 2 years ago
Chaotic ...
1. There is nothing inconsistent2. You are mixing up 2 MSG types
3. The behavior is related to the type
- Flyout = Info/Help/etc.
- Static = Warning/Error/etc.
Again: Why is this issue related to the image thing?
Updated by Kay Strobach almost 2 years ago
- File 28-06-2011_18-37-38.png added
mhmm the images are not the best.
for me there to many types of displaying an error in a form.
- see tceform
- see scheduler
- see extmgm
- others?
I added other sources/images. I think the core modules should use the same way of reporting an error. (anyway it's ok in the reportsmodule ...)
If you say it's ok - I'm fine ... :( but i learned that UI e.g. of forms should be consistent ;)
Updated by Steffen Gebert almost 2 years ago
- Flyout = Info/Help/etc.
- Static = Warning/Error/etc.
The problem that this is not true. It's an ugly technical thing that there are technically 2 types of Flashmessages (normal and ExtJS ones). Normal stay, ExtJS disappear.
There's no easy way to create a disappearing message from PHP - only from ExtJS. I tried to enable this few months ago, but it was rejected from few people. We could talk about this next week (putting it on my todo).
Updated by Kay Strobach almost 2 years ago
comment from steffen ;)
#23996 was it, I think - Discussion
Updated by Fabien Udriot almost 2 years ago
- Status changed from New to Closed
Is the discussion about what is the best "flyout messages" vs "inline message"?
I would favor "flyout messages" and would give it as global recommendation for all BE modules.
BTW, is this feature (flyout messages) documented somewhere?
Updated by Fabien Udriot almost 2 years ago
- Status changed from Closed to Needs Feedback
Updated by Kay Strobach almost 2 years ago
- http://typo3.org/documentation/document-library/core-documentation/doc_core_api/4.3.0/view/3/12/
- http://buzz.typo3.org/teams/core/article/43-treasure-trove-flash-messages/
- no documentation as far as i know ...
- there should be a page extension Development_Backend_Javascript ... Linked from here http://wiki.typo3.org/Extension_Development