noflo-ui
noflo-ui copied to clipboard
noflo
Visualize addressability of ArrayPort connections
Currently we show an ArrayPort in NoFlo UI simply as a port that can have multiple connections.
However, this doesn't show the fact that ArrayPort connections are individually addressable (see noflo/noflo#90). So instead of showing a single IN port, we should show:
IN[0]IN[1]
etc.
The component instance should always show one free port, so when you attach a connection, a new port should appear below it.
That's how I imagined it working, with new ports showing up as needed. Some visual grouping will help.
Is it an issue if [0] [1] [2] are connected, then [1] disconnects?
@forresto currently on ArrayPort.detach we re-index the ports, so they're always 0, 1, 2, ...
https://github.com/noflo/noflo/blob/master/src/lib/ArrayPort.coffee#L90
Visual example where this would be nice. With xpress/Router the incoming patterns and outgoing requests are matched by arrayport index.
Thinking about a vertical x horizontal way to visualize and d'n'd indices:
@automata that might be interesting for space-saving!
Original plan looked like this:
I at least think it should respect level-of-detail as set by the zoom level. Zoomed out far it should be one port, up close it should explode out.
I agree with one distinct inport/outport per connection like I have in my visualizations:
