frodovdr
/
node-red
mirror of https://github.com/node-red/node-red.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Created Design: Palette Management UI (markdown)

Nick O'Leary 2016-07-13 15:51:25 +01:00
parent a40b6c9240
commit b3a3fa27cc
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Design:-Palette-Management-UI.md Normal file

@ -0,0 +1,11 @@
The runtime admin api provides methods for managing the nodes in the runtime. Add/Remove (by npm module name) and Enable/Disable (at the module and node-set level).
We need to add a suitable UI component to the editor that allows the user to manage their palette.
The Add option should be provide search capability of the available nodes. Need to decide if this goes straight to npmjs.org or flows.nodered.org. The benefit of the latter is that we can define the query api and provide more details by default than the (un)official npmjs.org search API. Specifically, we can provide version information as part of the initial query, rather than having to do a secondary look-up for each result.
The downside of using flows.nodered.org is that it places a greater load on the site and adds a long-term dependency on the functionality of the site.
Regardless, the source of the query should be pluggable so it can be pointed at custom node libraries.
This also needs to consider what the upgrade story is for npm installed nodes. The UI could show which of the installed nodes have newer versions available. However, upgrading a node will require a restart (as does a complete removal).