Forrest O.

Let's not forget the floppy icon. What do you think about only saving on context switch? And a revert button in the component inspector?

I've been thinking that the search dropdown will be more like a CLI, so there could be an option there for "new component." 1. Select new component 2. Edit name,...

For the UI, I think that a special 'stub' type would make sense here. Then we could have - edit inports - edit outports - edit as component - edit...

Working on noflo/noflo-canvas#3 I've been imagining plugging a timeline to animate the values that make the drawings. I'm also imagining an output view, more complex than the current iframe+canvas, where...

The biggest design challenge with this proposal is where to put the labels. I agree that visually denoting params would be good. Another concept:  https://github.com/the-grid/the-graph/issues/197

I made that call for quick visual recognition when we switched from custom elements to svg/zui.

One thing to double-check is that ports should always be ordered as authored.

@bergie and @jonnor now it saves on [every change](https://github.com/noflo/noflo-ui/blob/776f91d64d217dfb8f8ab6a7507820f3056688f8/elements/noflo-component-editor.html#L188), what about saving only on leaving the editor? What should we do if there is lint at that point?

@bergie should we keep the `change` signal on every change and do the saving logic in noflo, or only send the `change` when leaving the editor?

Probably. I can look into it tonight.