To fit all 4 on one pic Search is unticked and I have used CSS to hide the footers, shrink the row height and draw a border round each. These tweaks make no difference to the column widths.
ui-table does not have a Class field. The CSS template has to be applied to the group.
While the defined column settings do make some difference, the widget certainly does not apply the specified widths.
When you change the table settings, the page is not correctly redrawn. It is especially prone to switch to the one attribute per row view. A page reload is vital.
Here is the last of the above tables (for comparison) and two tables with size set to 8x6
The widget occupies the specified screen real estate, note the gap between 4 and 5, but the table height collapses to show 1 (or less) rows
What I really want is to display two tables side by side on a Tab layout page, along the lines of the 2 charts side by side example in the documentation.
The table width does not respect the specified size
No data is displayed, and not even a scrollbar.
It's well over a year since the Flowfuse dashboard was released from beta testing, yet still it's riddled with small and huge bugs.
Frankly it is not worth spending any more time on.
Without a functional dashboard, what is the point of Node-red?
@jbudd - I decided to use ui-tabulator for my tables instead of ui-table in DB2. If your original tables were in ui-table (DB1), moving them to ui-tabulator is relatively easy (though it doesn’t fix some of the layout quirks of DB2). Let me know and I can document the steps that I took to move to ui-tabulator.
Not everyone wants/needs a dashboard. Fewer still need a Dashboard (capital D). Other options for data-driven UI’s exist and are stable but under ongoing improvements.
Just to address these two points, we are running on voluntary time, just as the initial Dashboard was for many years. We have very minimal community contributions outside of myself and Steve who are also only doing this in spare time.
For the “what’s the point of Node-RED”, fun fact, of the many, many instances we have running in FlowFuse, only about a third of those are actually running a Dashboard.
@joepavitt one addition to the ui-table node which would help is to Class option/msg.class.
Also are there any plans to replace the UX/UI engineer you had to let go?
@jbudd we’ve managed to build an app that relies extensively on ui-table and some custom css.
It has been a lot of trail and error and we have certain pages where groups move around like me on the dance floor.
Here’s hoping the recent survey might put some recourses back to the DB"2.
Not directly in the immediate future, however we should be transitioning some of the core FlowFuse dev team onto some Dashboard items over the next 4-6 weeks to try and get the backlog down, and add in some new features too (which will hopefully include replacing Chart.js with eCharts for performance improvements).
If you have any issue you can point me to, I’ll add it to our schedule.
