However the column width is now based on the text + Fil, resulting in a lot of white space, which results in tables not entering in the div.
Would it be possible to optionally remove this or maybe make it smaller?
The most important thing is having an overview. Like scrolling out in Excel gives an overview of the entire worksheet.
Table view is perfect if it comes to font size etc.
However:
Column width of the cells is based on the header. So there is a lot of white space. It would be way better to have multilined headers, rotated the headers and/or remove the “Fil” word, so the width is smaller.
A Table now always has a flex=100%, What if i have a table with 2 columns? It would be great to have a flex of 30% and have three tables next to eachother.
A table is now always dynamic. (allow add row/remove) As NumberFields are huge, i like to use tables with fixed size for input. With the first column the parameters name, the second/third the values. Now i use validations to prevent changes in the table. But it would be great to allow a static table, with first column not adjustable and prevent add/remove rows.
I think all of those do make valid feature requests. Or perhaps one bigger feature request that is something like “allow more fine grained control over table styling”. Your questions are a good example of the tradeoff we have to make: VIKTOR makes it very easy to create a UI around your tools. That easiness does cost you something: configurabillity. That tradeoff will always exist, but it’s always good to challenge it of course!
Do you currently get a lot of feedback from your end users about the styling of these tables in your editors?
Fair point, however besides being a platform to easily create UI, it should also be a platform which is easily to use.
And due to the lack of configurability it become tougher to create the overview (helicopter view) that certain technical users want.
Yes, the tables are great they say as they can combine input/output from Excel, work like Excel etc. So it is easy to use.
However
decimals are difficult to read.
Tables take up entire width and sometimes even generate horizontal scroll bars.
Lots of white space, due to big width headers
No multiline or symbols in tables
Sometimes it would be nice to have a reset button (we use a huge set params button for that)
They don’t know new rows can be added. (Right click was difficult to find at first)
It would be nice to have small static tables, like I said before.
But still it is way better than de Dynamic Array for end-use and development reasons:
Users: The overview is gone, only a close up view possible
Users: Copy paste a few rows, impossible
Developers: name argument isn’t present, so we can never ever move the table around as the data will be lost or we have to migrate.
So depending on the stakeholders, if they are engineers, I think the Table input should be one of the core features on the input side. As it helpt with the biggest bottleneck, changing a pattern/culture.