Design: Palette Management UI

Target: 0.15

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.

It needs to provide the following capabilities:

• 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

Secondary considerations

• modify node loading lifecycle so it only loads 'active' nodes - to maximise memory saving