Bug 8556 - Load tables can be overly wide in tlctl and Web Admin
Summary: Load tables can be overly wide in tlctl and Web Admin
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-26 13:42 CET by Linn
Modified: 2025-04-01 13:17 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments
The wide, spacious table in Web Admin (78.35 KB, image/png)
2025-03-26 13:42 CET, Linn
Details

Description Linn cendio 2025-03-26 13:42:47 CET
Created attachment 1268 [details]
The wide, spacious table in Web Admin

As part of doing bug 8543, the tables presenting load info now contain less data. This can make the load tables in tlctl and Web Admin look overly spacious, see details below.

1) In tlctl, when having several subclusters, the width of the table is adjusted to the subluster title, not the content of the table (since bug 8544). This makes the table look slightly off for long titles, see below:
> $ sudo tlctl load list
> Subcluster: "Default"
> ========================
> AGENT      USERS  STATUS
> ========================
> 127.0.0.1      0  UP    
> 
> Subcluster: "TestClusterVeryLongName123456789801234567898012345678980"
> ======================================================================
> AGENT                                    USERS  STATUS                
> ======================================================================
> 127.0.0.1                                    0  UP                    
2) In Web Admin under Status -> Load, the table fills out the whole width of the side. Personally, I think this table looks more off than the one in tlctl. This table only has 2 columns, and the table values are placed in with different adjustments, so that the values are as far apart as possible. See attachment for screenshot.

Note You need to log in before you can comment on or make changes to this bug.