General Improvements
Ideas for New Nodes
Specific Nodes that could be enhanced
--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Scott made the mistake of asking so here it is! The "quick" list of thoughts for NR!
Just my view of course with only a few days working seriously with NR so they have probably all been covered in the past.
General Improvements
- Debug window to have pop-up window with pretty JSON output or at least a link to display it. Currently really hard to debug msg content, especially when it gets bigger & more complex.
- Search for object by code, e.g.: 3e610b62.c19ef4 - helpful when you have a node you forgot to name but that is reporting an error!
- Save debug output switches (without needing a Deploy) - I think I've seen another discussion about this.
- Send/Receive msgs to itself (e.g. event based flows without needing MQTT broker) - via WS, internal events? A good way to avoid the desire for while loops? And to keep areas of concern separated.
- Socket.IO instead of raw web sockets - specifically to enable secured sockets?
- Secure login to admin portal. Out of the box. Far too much of the IoT world is ignoring security!
- Move admin to /admin by default and present a default front page. Making it easier to present a full application for new Node-Redders.
- HTTPS by default (with default certs that need to be changed)
- Move remaining node templates to NPM - currently not clear which are which
- Easier external edit for Function and Template nodes - already discussed in the previous thread.
Most likely a non-starter.
Ideas for New Nodes
- Time formatter - should be an easy one. Could use Moment.JS. Allow any allowed date/time format. Input field should be specifiable as should output field. Input should allow text. This is a really common transformation requirement!
- XML output - many web API's still demand XML.
- RSS output - shades of Yahoo! Pipes!! Possibly a nice way to collate and integrate many different
- A node to create/manage configuration nodes - save editing config files for static data
- Wrapper node - to keep node-sets together - with a title - cut/copy/move the wrapper keeps all the content together
- A "Dependency" node that doesn't trigger output until a set of inputs have been collected. This would allow an event to be triggered only after receiving several pieces of non-related or semi-related data (e.g. wait for 2 different web API's to return data before triggering output).
Specific Nodes that could be enhanced
- Better comment nodes - with HTML rich text - it is currently hard to document flows!
- Enable reordering of tests in Switch node - currently annoying when you started with a couple of entries plus an otherwise and then want to add something to the middle.
- More flexibility for JSON/XML nodes - ability to act on different parts (or whole) of msg
- MongoDB: Merge data into an existing entry - currently "update" seems to destroy any existing data so I currently have to have a node to read the existing data, combine the new data and then save the data.
- Ping that allows an external trigger. Also that allows multiple addresses - useful for checking if machines are alive. An ARP version of ping would also be very useful to enable checking if a SERVICE is alive on a device
On Tuesday, January 27, 2015 at 10:13:14 PM UTC+11, Julian Knight wrote:
Scott made the mistake of asking so here it is! The "quick" list of thoughts for NR!
General Improvements
...
- Secure login to admin portal. Out of the box. Far too much of the IoT world is ignoring security!
Not sure about this one, or the SSL. Most sensor networks are not secure, as such need to be on a secure network. The advantage of node-red is that it can be on that network, rather than the cloud. If it was default, I would have had to disable it.
Ideas for New Nodes
- Time formatter - should be an easy one. Could use Moment.JS. Allow any allowed date/time format. Input field should be specifiable as should output field. Input should allow text. This is a really common transformation requirement!
Easy, would you just change payload in and out? Or is it better to add this as a standard loaded in function to allow more flexibility ?
- XML output - many web API's still demand XML.
There is already an XML out, and Template - how would you do this one better? Since XML is infinite - how could you do something better than a template?
- RSS output - shades of Yahoo! Pipes!! Possibly a nice way to collate and integrate many different
- A "Dependency" node that doesn't trigger output until a set of inputs have been collected. This would allow an event to be triggered only after receiving several pieces of non-related or semi-related data (e.g. wait for 2 different web API's to return data before triggering output).
Socket.IO instead of raw web sockets - specifically to enable secured sockets?
--
Scott made the mistake of asking so here it is! The "quick" list of thoughts for NR!
Just my view of course with only a few days working seriously with NR so they have probably all been covered in the past.
General Improvements
- Debug window to have pop-up window with pretty JSON output or at least a link to display it. Currently really hard to debug msg content, especially when it gets bigger & more complex.
- Search for object by code, e.g.: 3e610b62.c19ef4 - helpful when you have a node you forgot to name but that is reporting an error!
- Save debug output switches (without needing a Deploy) - I think I've seen another discussion about this.
- Send/Receive msgs to itself (e.g. event based flows without needing MQTT broker) - via WS, internal events? A good way to avoid the desire for while loops? And to keep areas of concern separated.
- Socket.IO instead of raw web sockets - specifically to enable secured sockets?
- Secure login to admin portal. Out of the box. Far too much of the IoT world is ignoring security!
- Move admin to /admin by default and present a default front page. Making it easier to present a full application for new Node-Redders.
- HTTPS by default (with default certs that need to be changed)
- Move remaining node templates to NPM - currently not clear which are which
- Easier external edit for Function and Template nodes - already discussed in the previous thread.
Most likely a non-starter.
Ideas for New Nodes
- Time formatter - should be an easy one. Could use Moment.JS. Allow any allowed date/time format. Input field should be specifiable as should output field. Input should allow text. This is a really common transformation requirement!
- XML output - many web API's still demand XML.
- RSS output - shades of Yahoo! Pipes!! Possibly a nice way to collate and integrate many different
- A node to create/manage configuration nodes - save editing config files for static data
- Wrapper node - to keep node-sets together - with a title - cut/copy/move the wrapper keeps all the content together
- A "Dependency" node that doesn't trigger output until a set of inputs have been collected. This would allow an event to be triggered only after receiving several pieces of non-related or semi-related data (e.g. wait for 2 different web API's to return data before triggering output).
Specific Nodes that could be enhanced
- Better comment nodes - with HTML rich text - it is currently hard to document flows!
RED.nodes.registerType('',{ inputs:0, outputs: ['orSuccess', 'onError'] })
RED.nodes.registerType('',{ inputs:0, outputs: [ { name: 'orSuccess', desc: '' }, { name: 'onError', desc: 'This might be happening because the http endpoint is down...' } ] })
- Enable reordering of tests in Switch node - currently annoying when you started with a couple of entries plus an otherwise and then want to add something to the middle.
- More flexibility for JSON/XML nodes - ability to act on different parts (or whole) of msg
- MongoDB: Merge data into an existing entry - currently "update" seems to destroy any existing data so I currently have to have a node to read the existing data, combine the new data and then save the data.
- Ping that allows an external trigger. Also that allows multiple addresses - useful for checking if machines are alive. An ARP version of ping would also be very useful to enable checking if a SERVICE is alive on a device
Regards, Julian.
Here's my random comments!
- Better comment nodes - with HTML rich text - it is currently hard to document flows!
I'm hijacking that thought! I cloned and modified the comment node to be able to place it on a wire (not on NPM but I can put it up there). Technically speaking it's a node which takes a input and relay it to the output without doing anything with it. Of course this adds some overhead, but a microscopic one. However, this is really a hack-ish way of solving my real problem. My problem is that if I have a function with 10 different outputs, I want to be able to name the outputs (and maybe inputs) and make the names show on mouse over or something like that.
...
That we we could have backwards compatibility, checking if inputs/outs are numbers or arrays/objects.
That being said, I'd rather go for markdown than html rich text, but thats just me.
- Ping that allows an external trigger. Also that allows multiple addresses - useful for checking if machines are alive. An ARP version of ping would also be very useful to enable checking if a SERVICE is alive on a device
--
Oh well, can't say I'm that happy with the approach but I understand the reasons. It isn't the end of the world.
--
--
Thanks Julian... We do get to have some fun. Comments are off for a reason... and you wouldn't be able to sign up if you tried :) not got around to updating the template to hide that gorp.
Nick
Hi Ra,
Dave was working on a report-by-exception node that could be used in various scenarios like you describe. I'm not sure adding it to the switch node makes sense - we are always cautious about overloading a single node with too much behaviour that is best served by separating it out.
The http request node does allow you to set custom headers... pass in msg.headers as an object of header-name:value pairs. I think the sidebar help mentions that... but I'm on my phone so can't easily check from here. We don't allow you to set headers in the node config itself, but that's just down to not having got around to the fiddly ui work to make that a nice experience.
Regards,
Nick
The rbe node is here. https://www.npmjs.com/package/node-red-node-rbe
But the trigger node as mentioned is better for the once and once only use case (until reset).
Scott made the mistake of asking so here it is! The "quick" list of thoughts for NR!
Just my view of course with only a few days working seriously with NR so they have probably all been covered in the past.
General Improvements
- Debug window to have pop-up window with pretty JSON output or at least a link to display it. Currently really hard to debug msg content, especially when it gets bigger & more complex.
- Search for object by code, e.g.: 3e610b62.c19ef4 - helpful when you have a node you forgot to name but that is reporting an error!
- Save debug output switches (without needing a Deploy) - I think I've seen another discussion about this.
- Send/Receive msgs to itself (e.g. event based flows without needing MQTT broker) - via WS, internal events? A good way to avoid the desire for while loops? And to keep areas of concern separated.
- Socket.IO instead of raw web sockets - specifically to enable secured sockets?
- Secure login to admin portal. Out of the box. Far too much of the IoT world is ignoring security!
- Move admin to /admin by default and present a default front page. Making it easier to present a full application for new Node-Redders.
- HTTPS by default (with default certs that need to be changed)
- Move remaining node templates to NPM - currently not clear which are which
- Easier external edit for Function and Template nodes - already discussed in the previous thread.
Most likely a non-starter.
Ideas for New Nodes
- Time formatter - should be an easy one. Could use Moment.JS. Allow any allowed date/time format. Input field should be specifiable as should output field. Input should allow text. This is a really common transformation requirement!
- XML output - many web API's still demand XML.
- RSS output - shades of Yahoo! Pipes!! Possibly a nice way to collate and integrate many different
- A node to create/manage configuration nodes - save editing config files for static data
- Wrapper node - to keep node-sets together - with a title - cut/copy/move the wrapper keeps all the content together
- A "Dependency" node that doesn't trigger output until a set of inputs have been collected. This would allow an event to be triggered only after receiving several pieces of non-related or semi-related data (e.g. wait for 2 different web API's to return data before triggering output).
Specific Nodes that could be enhanced
- Better comment nodes - with HTML rich text - it is currently hard to document flows!
- Enable reordering of tests in Switch node - currently annoying when you started with a couple of entries plus an otherwise and then want to add something to the middle.
- More flexibility for JSON/XML nodes - ability to act on different parts (or whole) of msg
- MongoDB: Merge data into an existing entry - currently "update" seems to destroy any existing data so I currently have to have a node to read the existing data, combine the new data and then save the data.
- Ping that allows an external trigger. Also that allows multiple addresses - useful for checking if machines are alive. An ARP version of ping would also be very useful to enable checking if a SERVICE is alive on a device
Regards, Julian.
--