You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to the changes made to the Task Detail page for #411, the columns and values for the initial Tasks list should be made more visible to see key info in the rightmost columns. For example, with very long Location paths, all of the rightmost columns get hidden (I redacted most of the Location paths):
How should the problem be solved?
I think the columns and values for the initial Tasks list should be responsive to the width of the terminal UI, either by adding a ... prefix to make it fit in one line up to desired column width, or wrapping long values onto new lines if they don't fit (potentially args/options to set this preference?)
Any alternatives you've considered?
It may also be viable to simply instruct users via the README to only rely on info in the Task Detail view instead, but improving the initial UI to make columns more readable at a glance would greatly speed up our work.
How would users interact with this feature?
The UI ideally should automatically resize columns according to the width of the terminal that tokio console is running within. If there are options used to dictate the behavior (on whether to resize column widths at all, word wrap or use prefixes, etc.) they could take the form of args like:
MarcusHorn
changed the title
Improve Task Diagnostics UI for viewing Location and other columns
Improve Task Diagnostics UI readability for Location and other columns with dynamic widths
Jul 3, 2024
What problem are you trying to solve?
Similar to the changes made to the Task Detail page for #411, the columns and values for the initial Tasks list should be made more visible to see key info in the rightmost columns. For example, with very long
Location
paths, all of the rightmost columns get hidden (I redacted most of theLocation
paths):How should the problem be solved?
I think the columns and values for the initial Tasks list should be responsive to the width of the terminal UI, either by adding a
...
prefix to make it fit in one line up to desired column width, or wrapping long values onto new lines if they don't fit (potentially args/options to set this preference?)Any alternatives you've considered?
It may also be viable to simply instruct users via the README to only rely on info in the Task Detail view instead, but improving the initial UI to make columns more readable at a glance would greatly speed up our work.
How would users interact with this feature?
The UI ideally should automatically resize columns according to the width of the terminal that tokio console is running within. If there are options used to dictate the behavior (on whether to resize column widths at all, word wrap or use prefixes, etc.) they could take the form of args like:
Maybe also could make options about what specific column widths to use, like for
Location
for example.Would you like to work on this feature?
maybe
The text was updated successfully, but these errors were encountered: