Context of the issue

We want to get rid of all "toast" messages in the editor, because they are disturbing users.

Also it makes sense, that errors and warn-messages should be possible to still read later and see, what happened at what segment.

Therefore it makes sense to introduce an event logging grid in the editor, similar to that, what we have for a task in the PM overview.

To be implented

What to be logged

• all toast messages (they should only appear in the log in the future)
• all warnings and errors, that pop up at  the moment and need to be confirmed with "ok" or similar (they should still appear as pop-ups)
• NOT be logged should be warnings of the tag-check (they are anyway shown in the auto-qa)
• segment # in task

Where to be logged / Who can see it

Proposal: task event log. To be decided by Thomas, Pavel and Sylvi together. 
Decision: separate data structure, task event log wasn't used.

If we do that: Make sure, that

• all informational messages (toast messages so far) can only be seen in the event log inside the editor (not on pm level)
• warnings and errors happening inside the editor can be seen in the event log inside the editor AND on PM level
• messages of the task event log that have nothing to do with editing of the task can still only be seen in the event log of the PM
• (Thomas Implementation Hint: Implies separate data structure - we are talking here over UserNotifications, where some of them should go into the logging and some not)

UI design

Proposal:

• Grid in pop-up window, that still allows to interact with the stuff below it.
• Button in the toolbar above the grid, that shows the current number of info, warning and error messages (with icons which are visible if there's non-zero count of corresponding messages only)
• last message is shown in status bar - access to the grid via status bar
• evaluate possibility of placing of "status bar" into bottom left corner (not as part of accordion)
• clicking on an row (event of a segment) should scroll to the segment in the grid
• if the grid is opened, clicking on a segment in the segment table should scroll to the events connected to that segment in the grid if there are any