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

Controling the order of outgoing edges. #26

Closed
bzaborow opened this issue Feb 20, 2014 · 3 comments
Closed

Controling the order of outgoing edges. #26

bzaborow opened this issue Feb 20, 2014 · 3 comments

Comments

@bzaborow
Copy link

Hi,

I started to use the dagre-d3 for visualisation of data similar to one of examples (the Sentence Tokenization). Extending this example to display a DAG instead of a tree was super easy, but I've lost control of an order in which edges leave a particular node. Is it possible to restrict it somehow? If not, could you point me where to start looking into your code? For my data the order of edges is quite important.

In fact, it would be the best if i could constraint nodes order too (position from left to right in top down graph), but as I understand, it is not possible at the moment (issue #25 ?).

Thanks

@cpettitt
Copy link
Collaborator

It should be possible to add an order attribute to nodes and edges in the input graph to indicate to dagre what the ordering for edges and nodes should be. This information could be used in the order phase instead of the barycenter heuristic. The implementation should be much simpler than that required for #25.

I'd be interested in what drives the requirement for edge ordering if you're at liberty to describe it. I can already imagine several reasons for wanting to explicitly order the nodes, though.

@cpettitt
Copy link
Collaborator

Oh, this should be moved to dagre. It shouldn't require any work in dagre-d3.

@cpettitt
Copy link
Collaborator

Closing in favor of dagrejs/dagre#112

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

No branches or pull requests

2 participants