[ 
https://issues.apache.org/jira/browse/ARTEMIS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Bertram updated ARTEMIS-2541:
------------------------------------
    Description: 
The accompanying PR improves the following parts of the Admin UI's message 
browser:
 # use fixed column width for columns with date/numeric/boolean values
 # move the *userID* column to the end and make it's width auto expand
 # the *userID* column now alternatively displays the *_AMQ_VALIDATED_USER* 
string property in case the userID field is empty. this e.g. is the case in our 
environment where we use client certificate based authentication.
 # display human readable names in the *type* column instead of numeric value. 
the numeric value is still accessible via a tooltip of the respective cell and 
used for sorting
 # The *expires* column displays a human friendly representation of the time 
when the message expires (or expired in case it was not yet GCed) instead of a 
unix timestamp.
 If the message expires in less than 24 hours the format "*In hh:mm:ss*" is 
used, otherwise the format is "*yyyy.mm.dd hh:mm:ss*" in the local user's 
timezone.
 The actual timestamp value with ms precision is still used when sorting the 
columns and is accessible via a cell tooltip.
 # The messages are now sortable by the *timestamp* column, as the server now 
sends the unix timestamp instead of an already pre-rendered datetime string in 
the server's locale
 # Add a new sortable column that displays the messages persistent size.

Here is screen-shot from before the changes:
*!ScreenShot_BeforePR.jpg|thumbnail!*

Here is a screen-shot from after the changes:
!ScreenShot.png|thumbnail!

  was:
The accompanying PR improves the following parts of the Admin UI's message 
browser:
 # use fixed column width for columns with date/numeric/boolean values
 # move the *userID* column to the end and make it's width auto expand
 # the *userID* column now alternatively displays the *_AMQ_VALIDATED_USER* 
string property in case the userID field is empty. this e.g. is the case in our 
environment where we use client certificate based authentication.
 # display human readable names in the *type* column instead of numeric value. 
the numeric value is still accessible via a tooltip of the respective cell and 
used for sorting
 # The *expires* column displays a human friendly representation of the time 
when the message expires (or expired in case it was not yet GCed) instead of a 
unix timestamp.
 If the message expires in less than 24 hours the format "*In hh:mm:ss*" is 
used, otherwise the format is "*yyyy.mm.dd hh:mm:ss*" in the local user's 
timezone.
 The actual timestamp value with ms precision is still used when sorting the 
columns and is accessible via a cell tooltip.
 # The messages are now sortable by the *timestamp* column, as the server now 
sends the unix timestamp instead of an already pre-rendered datetime string in 
the server's locale
 # Add a new sortable column that displays the messages persistent size.

Here is screen-shot from before the changes:
!ScreenShot_BeforePR.jpg|thumbnail!

Here is a screen-shot from after the changes:
!ScreenShot.png|thumbnail!


> Improve rendering in message browser of Admin UI
> ------------------------------------------------
>
>                 Key: ARTEMIS-2541
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2541
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Web Console
>    Affects Versions: 2.10.1
>            Reporter: Sebastian T
>            Priority: Minor
>         Attachments: ScreenShot.png, ScreenShot_BeforePR.png
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> The accompanying PR improves the following parts of the Admin UI's message 
> browser:
>  # use fixed column width for columns with date/numeric/boolean values
>  # move the *userID* column to the end and make it's width auto expand
>  # the *userID* column now alternatively displays the *_AMQ_VALIDATED_USER* 
> string property in case the userID field is empty. this e.g. is the case in 
> our environment where we use client certificate based authentication.
>  # display human readable names in the *type* column instead of numeric 
> value. the numeric value is still accessible via a tooltip of the respective 
> cell and used for sorting
>  # The *expires* column displays a human friendly representation of the time 
> when the message expires (or expired in case it was not yet GCed) instead of 
> a unix timestamp.
>  If the message expires in less than 24 hours the format "*In hh:mm:ss*" is 
> used, otherwise the format is "*yyyy.mm.dd hh:mm:ss*" in the local user's 
> timezone.
>  The actual timestamp value with ms precision is still used when sorting the 
> columns and is accessible via a cell tooltip.
>  # The messages are now sortable by the *timestamp* column, as the server now 
> sends the unix timestamp instead of an already pre-rendered datetime string 
> in the server's locale
>  # Add a new sortable column that displays the messages persistent size.
> Here is screen-shot from before the changes:
> *!ScreenShot_BeforePR.jpg|thumbnail!*
> Here is a screen-shot from after the changes:
> !ScreenShot.png|thumbnail!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to