Node-RED Survey: Shaping the Future of Node-RED's User Experience

News
21

No it doesn't, I just never use it because it's not integrated into Node-RED itself. Just as I don't like copying flow json titbits from the forum to Node-RED just to look at the flow. This is just me, I don't like the extra steps when everything could be done better directly inside Node-RED.

If I could search flows on flows.nodered.org via an interface in Node-RED then I'd be happy. If I could then upload my flows to flows.nodered.org using a single button inside of Node-RED, I would be even more happy. If I could then visually compare versions of flow code inside Node-RED well then I would have FlowHub. Because that's what FlowHub does.

I know flows.nodered.org doesn't do these things and I know I could have made these changes over at flows.nodered.org but flows.nodered.org isn't coded in Node-RED and that was part of the exercise: create extensions for Node-RED in Node-RED.

But that's not what I'm looking for, I'm looking for Node-RED integration. Not a searchable website. Just as the node packages are beautifully integrated into Node-RED - in fact the inspiration for better flow integration - why not the same for libraries of shared flows?

I don't understand why a better integration of flows and flow libraries into Node-RED is such an uphill discussion. And besides, I don't care about what the other kids across the street are playing, I want to play Node-RED and I want to play it efficiently. No switching between my Emacs and Node-RED when I'm developing nodes for Node-RED. No switch browser tabs to copy code from GitHub or wherever, all my flow code is integrated in Node-RED as a list and checked in on GitHub - version control and visual code. And all coded in Node-RED.

Sorry, but this discussion started back about two years ago when I asked whether there was a way to visual flow json files in a browser without Node-RED. The answer was: no and if it was easy, then it would have been done already. It took me all of a week to have an initial version of the flowviewer completed. Which, after those two years, is now integrated here (btw thanks again for doing that :)).

Only two years. So I assume that FlowHub will also take another two years before it catches on. So what. In the meantime, I'll just keep working on Erlang-Red, which has already created a certain resonates within the Erlang/BEAM community.

Plus because all the coding I did with FlowHub, I can seamlessly transfer flow code between Erlang-Red and Node-RED to create a library of tests to verify that I'm matching Node-RED functionality in Erlang-Red.

Here's another idea: lets create suite of visual unit tests that ensure that node functionality is maintained between versions? The test suite above is a start.

1 Like
22

image
image802Ɨ315 28.4 KB

Here you forced me to lie because I don't use NR dashboards.

23
  • add a terminal like the one found in vscode.
  • allow reorgazing panels
  • add floating/detachable pallete like the one found in gimp
24

You can search nodes, maybe the pallete should be extended to flows to? Most nodes are searched via github i think though, or maybe npm. Either way you can get from node-red pallette to flow library each node has a link.

25

Better integration of the flow library and the editor has long been something we want to do. It just hasn't happened yet. I linked to an issue with some improvement suggestions - that wasn't a exhaustive list, but a starting point.

I don't want to get too drawn into specific features in this thread as it's meant to be focussed on the broader survey. There will certainly be a time for getting into details.

3 Likes
26

@dimitrieh

The question ' What other automation tools do you use? (Select all that apply)' - what if users have only used node-RED (like me!). Selecting 'just node-RED' the survey forces uses to add comparative scores for the following 4 questions (when I have no other automation tool to compare with). I entered a midway score for each - just to complete the survey.

Also...

The last question ' Would you like to stay involved? (Optional)' only allows one answer. Wouldn't it be better if multiple responses was possible?

1 Like
27

Thank you for the survey. Please carefully consider the impact of introducing AI. IMHO, the risks are greater than potential benefits.

1 Like
28

Great survey. Several questions made me think of ideas that I hadn't considered before. I'm looking forward to seeing what comes of this.

29

Sorry and thanks for reporting! Updated this to an optional question!

30

Amazing! And please do tell! Any information and ideas that came up would be lovely to see posted here :folded_hands:

31

Thanks! The survey has been updated accordingly so the workaround is no longer necessary. And the other one is now possible!

1 Like
32

Survey filled in! I consider myself an avid hobby user that use Node-RED extensively for home automation. Iā€™m an advocate that always speaks in favor of Node-RED over other alternatives. However, my biggest grip, by far, is the lack for building stunning and modern UIs without spending a ton of time. Iā€™m still resorting to the original dashboards because I find it easiest but it lacks in many aspects.

33

I added all of my ideas to the appropriate spots in the survey. I donā€™t think I could reproduce them here without going back and looking at my answers. lol.