Invisible wrote:
>>> But it's just the implication that this is impossibly difficult that 
>>> bothered me. How long can it possibly take to try all possible 
>>> permutations of 10 nodes?
>>
>> Really, try implementing a brute force algorithm and see for yourself 
>> how it scales.  Ten nodes may work, but what about twenty?
> 
> Ah, I see. So you mean the problem is that *other people* might try to 
> draw big graphs with it?

Heh, yeah I suppose that's the idea.  I think that "works with graphs of 
up to 12 nodes!" is maybe not the best feature for a piece of software 
to have.


>> If I remember correctly you wanted to draw trees though?  Edge 
>> crossings certainly wouldn't be a problem there.
> 
> Trees that occasionally have nodes pointing back to their ancesters, 
> yes. ;-)

Ahh, that makes sense.  If I remember you didn't want to order of the 
nodes to be able to change, in which case you really don't have as much 
choice


> Weirdly, GraphViz manages to come up with some *really* strange layouts 
> - and refuses to obey my hints to lay the graph out the way I actually 
> want it...

I haven't actually used the program, so I unfortunately can't be of much 
help here.  Since you have a small graph and pretty specific formatting 
requirements, what happened with the app you were writing yourself to do 
the layout?  You could also just draw it in inkscape of course if you 
want a really exact layout.

Post a reply to this message