Re: [Pharo-project] [Moose-dev] Roassal new algorithms

2013-04-20 Thread Frank Shearar
Sure, and I had to discover that for myself, since the d3 example was titled "flare imports". I only found out about the name "hierarchical bundled edges" thanks to Alexandre's original post! frank On 20 April 2013 07:23, Tudor Girba wrote: > This visualization is precisely made for hierarchical

Re: [Pharo-project] [Moose-dev] Roassal new algorithms

2013-04-20 Thread stephane ducasse
On Apr 20, 2013, at 8:23 AM, Tudor Girba wrote: > This visualization is precisely made for hierarchical graphs. That is why the > edges are called "hierarchical bundled edges". So, yes, you need a > hierarchical graph. +1 :) > > Cheers, > Doru > > > On Apr 19, 2013, at 8:57 PM, Alexandr

Re: [Pharo-project] [Moose-dev] Roassal new algorithms

2013-04-19 Thread Tudor Girba
This visualization is precisely made for hierarchical graphs. That is why the edges are called "hierarchical bundled edges". So, yes, you need a hierarchical graph. Cheers, Doru On Apr 19, 2013, at 8:57 PM, Alexandre Bergel wrote: > This is a very cool visualization. There is no reason why w

Re: [Pharo-project] [Moose-dev] Roassal new algorithms

2013-04-19 Thread Frank Shearar
On 19 April 2013 20:39, Igor Stasenko wrote: > On 19 April 2013 21:33, Frank Shearar wrote: >> Oh absolutely! >> >> My comment comes from trying to analyse the dependencies between >> classes in my SIP stack [1]. What I found was that simply mapping >> dependencies in a flat namespace (as Delphi

Re: [Pharo-project] [Moose-dev] Roassal new algorithms

2013-04-19 Thread Igor Stasenko
On 19 April 2013 21:33, Frank Shearar wrote: > Oh absolutely! > > My comment comes from trying to analyse the dependencies between > classes in my SIP stack [1]. What I found was that simply mapping > dependencies in a flat namespace (as Delphi has) resulted in a tangled > mess. > Oh.. SIP. RTP/RT

Re: [Pharo-project] [Moose-dev] Roassal new algorithms

2013-04-19 Thread Frank Shearar
Oh absolutely! My comment comes from trying to analyse the dependencies between classes in my SIP stack [1]. What I found was that simply mapping dependencies in a flat namespace (as Delphi has) resulted in a tangled mess. Then I added the unit name to the classes, so I had, say, IdSipTransport.T

Re: [Pharo-project] [Moose-dev] Roassal new algorithms

2013-04-19 Thread Alexandre Bergel
This is a very cool visualization. There is no reason why we cannot do it in Pharo Alexandre On Apr 19, 2013, at 10:49 AM, Frank Shearar wrote: > I've played with these before [1]. They work best with hierarchical names. In > other words, in a flat namespace (say, showing class dependencies