It would be helpful to allow display names for columns in the UI that are different from the actual column names, such as displaying a ChangePct column as Chg% in the UI. We should support names that are not valid Java identifiers too (such as names including spaces or symbols like %/&/etc.)
If you hover over the column headers, you should be able to see the underlying real column name.
Even better would be if multiple column names could be specified, with the UI using the longest name that fits the column's current width in the UI. So as you make a column narrower, its name would update to use a shorter name that fits (so we can avoid truncating and adding ...):
ProcessInfoId -> PIId
Change% -> Chng% -> Chg%
MarketCap -> MktCap
GICSIndustryGroup -> IndustryGroup -> IndGroup
Example of what happens now:
This would be helpful because longer and more descriptive column names are really helpful when familiarizing yourself with a table and figuring out what you want in a dashboard, but once you generally know what's in a table, you want to make the columns as narrow as possible so that you can fit the most data possible on the screen. (Somewhat related to https://github.com/deephaven/web-client-ui/issues/1486.)
It would be helpful to allow display names for columns in the UI that are different from the actual column names, such as displaying a
ChangePct
column asChg%
in the UI. We should support names that are not valid Java identifiers too (such as names including spaces or symbols like%
/&
/etc.)If you hover over the column headers, you should be able to see the underlying real column name.
Even better would be if multiple column names could be specified, with the UI using the longest name that fits the column's current width in the UI. So as you make a column narrower, its name would update to use a shorter name that fits (so we can avoid truncating and adding
...
):ProcessInfoId
->PIId
Change%
->Chng%
->Chg%
MarketCap
->MktCap
GICSIndustryGroup
->IndustryGroup
->IndGroup
Example of what happens now:
This would be helpful because longer and more descriptive column names are really helpful when familiarizing yourself with a table and figuring out what you want in a dashboard, but once you generally know what's in a table, you want to make the columns as narrow as possible so that you can fit the most data possible on the screen. (Somewhat related to https://github.com/deephaven/web-client-ui/issues/1486.)