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

Ways of Exploring the Network #7

Open
carmen-tm opened this issue May 23, 2014 · 1 comment
Open

Ways of Exploring the Network #7

carmen-tm opened this issue May 23, 2014 · 1 comment

Comments

@carmen-tm
Copy link
Contributor

Doubts about Ways of exploring the Full Network, in order to allow them on the Network Stage: Full and Partial Networks
How would users expect to explore the Network, in order to give them the most useful interface? My go:
waysexploringnetwork sketch

  • Step by Step -> Path drawing case. The user defines the route as far as explores the network by clicking on the nodes consecutively. Contextual Menu options will allow to perform specific graph actions (filtering, neighbors, etc) as on this dagre+d3 example to support the exploration. That will define a highlighted pathway on the network that will be updated as tree map/path diagram on the Route Map.
  • Target defined -> Path finding case. The user already knows the info is looking for, and how is called. He writes it on a Search element (_ _ _ _) and the nodes/edges required are highlighted on the network. By selecting one, a Contextual Menu option will allow to perform again specific graph actions plus the shortest pathway to the root, and maybe more path alternatives. Again, when clicking/accepting, the network will shows a path drawing highlighted that will be updated as tree map diagram on the Route Map.

Are those 2 cases right? Any other thought to have in mind about what the users would expect or how they would like to interact with the network? Any other case?

(Optional) Making those 2 ways complementaries. Allowing to mix a handy selection (step by step case) and find by the text search element another node (target defined case) and short paths connecting the selections.

@eparejatobes
Copy link
Member

Agreed in general. I think it would be really helpful to have minimum spanning trees/forests for a set of types.

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

2 participants