Dashboard 2 Table Woes

[jbudd]

These 4 tables are shown on a Grid layout page. The Group is size 12x1 and the table sizes are all Auto.

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.

1. ui-table does not have a Class field. The CSS template has to be applied to the group.
2. While the defined column settings do make some difference, the widget certainly does not apply the specified widths.
3. 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

4. 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.

Here are two tables 6x6 on this page (No CSS applied on this page)

5. The table width does not respect the specified size
6. 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?

[rakgupta]

@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.

[TotallyInformation]

@jbudd

Without a functional dashboard, what is the point of Node-red?

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.

[joepavitt]

@jbudd

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?

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.

[Bobo]

@joepavitt

we are running on voluntary time

I thought you hired someone to work on it a while back?

FlowFuse is Hiring: Full Time Front-End Engineer for Dashboard 2.0

Hi All, we are in a fortunate position to be growing our engineering team again at FlowFuse, and hiring a full-time front-end engineer to come and work at FlowFuse, and lead the FlowFuse Dashboard (Dashboard 2.0) project. If you're interested, or maybe know somebody else that may be, then please do reach out or send in a job application through: Job Opening - Front-End Engineer, Node-RED Dashboard 2.0 • FlowFuse

[joepavitt]

@Bobo

I thought you hired someone to work on it a while back?

We did, in October, as I shifted into another role in FlowFuse, but unfortunately we had to let them go after 6 weeks.