Updated Design: Palette Management UI (markdown)

Design:-Palette-Management-UI.md

@@ -2,10 +2,15 @@ The runtime admin api provides methods for managing the nodes in the runtime. Ad
 
 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.
+It needs to provide the following capabilities:
 
-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.
+ - See what nodes are currently installed - and the module that provides them
+ - Enable/Disable any of those nodes - bearing in mind the granuality of enable/disable is the nodeset
+ - Uninstall any of those nodes - at the module level
+ - Browse a catalog of available nodes and install any of them
+ - Allow custom catalogs to be provided - via `settings.js` - either in addition to, or in replacement of the default catalog
+ - ??? Allow the user to provide a custom catalog url in the editor and then browse its catalog
 
-Regardless, the source of the query should be pluggable so it can be pointed at custom node libraries.
+Secondary considerations
 
-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).
+ - modify node loading lifecycle so it only loads 'active' nodes - to maximise memory saving