Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Component port filtering #275

Open
chadrik opened this issue May 23, 2016 · 1 comment
Open

Component port filtering #275

chadrik opened this issue May 23, 2016 · 1 comment

Comments

@chadrik
Copy link

chadrik commented May 23, 2016

Here are some ideas on how to deal with components with many ports, borrowed from Autodesks' maya:

maya_node_graph_expand_contract

Here's what's going on:

Each node has a 3-state toggle menu in the upper-right hand corner that controls port display. the states are:

  1. collapse all ports to one "omni" input port and one "omni" output port
  2. show connected ports only
  3. show all ports

I think we only need modes 2 and 3. As a user, I would set my components to show "all ports" when editing the graph so that it's easy to connect new edges, and then when running and monitoring the graph I would set components to "connected-only" mode so that it's more condensed. Maybe noflo-ui could automatically switch between modes depending on whether the graph is running or not?

Here's another feature that allows ports to be filtered by name:

maya_node_graph_filtering

Might be overkill for now, but thought I'd throw it out there.

@djdeath since you are another user who has components with many ports, what do you think of these ideas?

@forresto
Copy link
Collaborator

VIzor.io has something similar with node collapsing:

vizor-node-collapse

Filtering would be next-level, maybe only enabled on nodes with > 9 ports or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants