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

Ranking to prefer shorter edges #14

Closed
marcello3d opened this issue Dec 10, 2013 · 4 comments
Closed

Ranking to prefer shorter edges #14

marcello3d opened this issue Dec 10, 2013 · 4 comments
Labels

Comments

@marcello3d
Copy link

Hello again!

I've run into this situation where it seems to be snapping parts of the tree to the top of the screen resulting in long edges:

digraph {
  a1->a2->a3->a4->a5->a6->o
  b1->o
  c1->c2->o
  d1->d2->d3->o
}

screen shot 2013-12-10 at 11 36 43 am

Here's the same graph on graphviz's dot command:
test

It's not entirely sure which approach is better, but it seems like the 'b1' node should be at the top, or the rest should aligned to the bottom.

Thanks for your time.

@cpettitt
Copy link
Collaborator

I think the dot approach is a little easier to read since the eye doesn't have to move as much for the edges. Also, shorter paths will result in faster rendering. This is actually a bug in dagre itself.

@marcello3d
Copy link
Author

Whoops. I must have just autocompleted to the wrong github url! Do you want me to move the issue over?

@cpettitt
Copy link
Collaborator

Sure, if you don't mind.

Thanks!

Sent from my iPhone

On Dec 11, 2013, at 15:26, Marcello Bastéa-Forte notifications@github.com wrote:

Whoops. I must have just autocompleted to the wrong github url! Do you want me to move the issue over?


Reply to this email directly or view it on GitHub.

@marcello3d
Copy link
Author

moved to dagrejs/dagre#105

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

No branches or pull requests

2 participants