New release :
13 Sep 12:42:43 - [info] Node-RED FlexDash plugin version 0.4.105
13 Sep 12:42:44 - [info] Node-RED FlexDash version 0.4.105
13 Sep 12:42:44 - [info] Node-RED FD Core Widgets version 0.4.46
13 Sep 12:42:46 - [info] FlexDash UI version 0.4.61
Please update node-red-corewidgets in addition to node-red-flexdash. And refresh any open browser windows.
To install FlexDash from scratch or for other help, please refer to the documentation,
especially the quick start section.
Fixes :
- k for kilo in stat widget
- support for precision in stat widget
- fix colors (supporting names like purple-darken-4)
- fix error caused by moving widgets in FD when there are disabled widgets
- fixes for scrolling of tables and also in pop-ups, still not 100%
- added sorting to simple-table
Not fixed :
- Use msg.payload in label widget and a bunch more
- Sparkline doesn't handle 0 value input correctly
- fix redirect for URL without slash and query string, e.g.,
http://localhost:1880/flexdash/?theme=dark
- find a fix for loopback, e.g. toggle node (work-around: please disable loopback and use wires & junction node to loop back in the flow)
- did I forget something?
Musings :
I'm pondering a bit about the component hierarchy in FlexDash. Right now there are tabs, grids and widgets. Tabs and grids are containers (contain other FD components), widgets are leaves in that tree. Except for panels, which are widgets but contain other widgets, a bit of a hack. So there are 3 levels in the tree (tabs, grids, widgets) or sort of 4 with the panel hack.
I'm wondering whether I should scrap all this and just have widgets and remove any built-in notion of tabs and grids and make it so a widget may or may not contain other widgets. (I may keep the notion of tabs 'cause they tie into nav and other rather special stuff, could allow to plug in a different implementation with different representation, though).
I believe this would simplify the code base somewhat and it would make FD more flexible 'cause at some level it then allows pretty arbitrary types of web pages to be built. On the other hand, a bunch of weeks would disappear into making this change. The good news is that by and large such a change would not be that disruptive in that the widgets that display stuff wouldn't really have to change and the NR nodes would also remain the same (grids and panels are already both "fd_container"). So I'm inclined to push forward as-is and worry about the refactoring when there's a bigger push to try alternate page layouts.
As always, I'm sure you will let me know about issues