Dashboard and UIs for Node-Red
dashboard.flowfuse.com
Dashboard and UIs for Node-Red
1–8 of 8 posts
Re: Dashboard and UIs for Node-Red
#2At first I thought this was a new version of the "officially" supported node-red-dashboard [1], but that doesn't seem to be the case. The landing page doesn't seem to indicate it is different, but clicking through Getting Started they differentiate. All the screenshots look very similar to the vanilla dashboard, but looking at the two githubs [2][3] shows it isn't a lazy fork. Could anyone from flowfuse shed light on how their version is different?
[1] https://flows.nodered.org/node/node-red-dashboard
[2] https://github.com/node-red/node-red-dashboard/tree/master
Re: Dashboard and UIs for Node-Red
#3At first I thought this was a new version of the "officially" supported node-red-dashboard [1], but that doesn't seem to be the case. The landing page doesn't seem to indicate it is different, but clicking through Getting Started they differentiate. All the screenshots look very similar to the vanilla dashboard, but looking at the two githubs [2][3] shows it isn't a lazy fork. Could anyone from flowfuse shed light on…
From what I understand the original dashboard is based on Angular v1 which is not maintained anymore.
This would be the main reason for the rewrite...
Re: Dashboard and UIs for Node-Red
#4Words like flow, fuse, etc are really trending these days with startups, I note.
Re: Dashboard and UIs for Node-Red
#5At first I thought this was a new version of the "officially" supported node-red-dashboard [1], but that doesn't seem to be the case. The landing page doesn't seem to indicate it is different, but clicking through Getting Started they differentiate. All the screenshots look very similar to the vanilla dashboard, but looking at the two githubs [2][3] shows it isn't a lazy fork. Could anyone from flowfuse shed light on…
> The original Node-RED Dashboard is based on Angular v1, which is no longer maintained. Although small patches have been and will continue to be applied on a "best can do" basis, there will be no major feature upgrades. The lack of ongoing maintenance and updates has the potential to lead to underlying security breakages, a risk we are not comfortable taking. We have recognized the need to innovate and adapt, which is why we are creating a completely new project to replace the existing Node-RED Dashboard.
Re: Dashboard and UIs for Node-Red
#6At first I thought this was a new version of the "officially" supported node-red-dashboard [1], but that doesn't seem to be the case. The landing page doesn't seem to indicate it is different, but clicking through Getting Started they differentiate. All the screenshots look very similar to the vanilla dashboard, but looking at the two githubs [2][3] shows it isn't a lazy fork. Could anyone from flowfuse shed light on…
The original ("v1") Node-RED Dashboard is now deprecated
https://discourse.nodered.org/t/node-red-dashboard-v1-deprec...
Re: Dashboard and UIs for Node-Red
#7At first I thought this was a new version of the "officially" supported node-red-dashboard [1], but that doesn't seem to be the case. The landing page doesn't seem to indicate it is different, but clicking through Getting Started they differentiate. All the screenshots look very similar to the vanilla dashboard, but looking at the two githubs [2][3] shows it isn't a lazy fork. Could anyone from flowfuse shed light on…
Hi, I'm the lead developer on FlowFuse's Dashboard - thanks for the question.
We have had to restart the project from scratch due to the original Node-RED Dashboard's (I'll call this Dashboard 1.0) Angular 1 dependency. We couldn't fork.
That being said, because of how widely adopted and popular Dashboard 1.0 is, we wanted to make sure we mimicked that user experience as much as possible, so that users familiar with 1.0 felt comfortable with 2.0, but still ensured we made improvements in areas, where appropriate. Hence, there is a lot of crossover with the same, familiar nodes (plus a fair few more).
FlowFuse are actively developing and supporting Dashboard 2.0, and it's here to stay. It can be considered the "official" next phase of Dashboard 1.0. Nick, the co-creator of Node-RED, is FlowFuse's CTO, and FlowFuse ourselves are contributing heavily to the Node-RED project.
I wrote this up today: https://flowfuse.com/blog/2024/06/dashboard-1-deprecated/#wh... which gives a summary of the key differences, what we have planned, and how to get started.
Re: Dashboard and UIs for Node-Red
#8At first I thought this was a new version of the "officially" supported node-red-dashboard [1], but that doesn't seem to be the case. The landing page doesn't seem to indicate it is different, but clicking through Getting Started they differentiate. All the screenshots look very similar to the vanilla dashboard, but looking at the two githubs [2][3] shows it isn't a lazy fork. Could anyone from flowfuse shed light on…
Hi, I'm the lead developer on FlowFuse's Dashboard - thanks for the question. We have had to restart the project from scratch due to the original Node-RED Dashboard's (I'll call this Dashboard 1.0) Angular 1 dependency. We couldn't fork. That being said, because of how widely adopted and popular Dashboard 1.0 is, we wanted to make sure we mimicked that user experience as much as possible, so that users familiar with…
Thank you so much for the quick answer. That makes complete sense. I appreciate anyone putting in efforts in on Node-RED. I use it heavily in interactive museum exhibits and would spend a lot more time on software "plumbing" without it. Dashboard 1 has been very useful, but definitely starts to struggle on things like graphs with 3000+ points. I look forward to trying out this new one!