Improve Pulse (MGNLUI-1397)

[MGNLUI-83] Implement visual design for the messages list Created: 02/Oct/12  Updated: 19/Jun/13  Resolved: 22/May/13

Status: Closed
Project: Magnolia UI
Component/s: design, pulse
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Sub-task Priority: Neutral
Reporter: Mikaël Geljić Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-1050 Informational messages should increas... Closed
Template:
Date of First Response:
Sprint: Beta 3

 Description   

http://wiki.magnolia-cms.com/display/UX/Style+guides+for+the+Magnolia+shell#StyleguidesfortheMagnoliashell-Messageslistandgenerallistofitems



 Comments   
Comment by Christopher Zimmermann [ 24/May/13 ]

Implementation looks good but theres a problem.

On any operation with pulse view we get multiple messages in log:

WARNING: You are using IndexedContainerProperty.toString() instead of getValue() to get the value for a IndexedContainerProperty. This will not be supported starting from Vaadin 7.1 (your debugger might call toString() and cause this message to appear).
May 24, 2013 11:33:45 AM com.vaadin.data.util.IndexedContainer$IndexedContainerProperty toString

This occurs whether running in debug mode or not, so i dont think its a debugger issue.

I tested on master and dont get these warnings - so it must be something introduced in the branch.

Ideally the warnings would not be generated at all. But if there is a good argument, then at the least we need a new ticket with explicit notice on what change in this branch is causing the warnings. I spent a while trying to track down the change that introduced them but could not.

Maybe its a clue that when a column is resorted - you get two of these warnings for each message in the list.

Generated at Mon Feb 12 08:33:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.