6 May
2013
6 May
'13
1:43 p.m.
Hi
I've made kind a big refactoring in Roassal-Algorithm, as I've
learnt that ROContainer's attributes was there for any kind of use, now
the CompactTree family uses it, there are new methods for ROElement in
the package, but no more need of ROCompactTreeNode (former RONode).
In
the same time, I've written tests to be sure that the code still works
(in fact it's the aim of tests I think).
So now, there ain't crossing
any more, in LaggeredTree.
Tell me what kind of new layout you wish to
see in Roassal, maybe you can have a look at D3 library.
Or maybe I
will start looking at how to increase roassal scalability.
Just tell
Regards
Mathieu
6 May
6 May
3:24 p.m.
Hi!
Thanks!!
treeSetUp has a "self halt",
I also see that your package Roassal-Algorithm contains a class RORadialTreeLayout_N. I
have included this class some times ago and renamed it as RORadialTreeLayout. Apparently
RORadialTreeLayout_N and RORadialTreeLayout are still the same. If you want to update you
RORadialTreeLayout_N, no problem, but I have slightly improved your code.
Let me know when you feel your code is ready. I have tried your example and I like it very
much. It should be part of Roassal.
Alexandre
On May 6, 2013, at 7:43 AM, mathieubmddehouck(a)mailoo.org wrote:
Hi
I've made kind a big refactoring in Roassal-Algorithm, as I've learnt that
ROContainer's attributes was there for any kind of use, now the CompactTree family
uses it, there are new methods for ROElement in the package, but no more need of
ROCompactTreeNode (former RONode).
In the same time, I've written tests to be sure that the code still works (in fact
it's the aim of tests I think).
So now, there ain't crossing any more, in LaggeredTree.
Tell me what kind of new layout you wish to see in Roassal, maybe you can have a look at
D3 library.
Or maybe I will start looking at how to increase roassal scalability.
Just tell
Regards
Mathieu
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
5:03 p.m.
mathieubmddehouck(a)mailoo.org wrote:
Hi
I've made kind a big refactoring in Roassal-Algorithm, as I've
learnt that ROContainer's attributes was there for any kind of use, now
the CompactTree family uses it, there are new methods for ROElement in
the package, but no more need of ROCompactTreeNode (former RONode).
In
the same time, I've written tests to be sure that the code still works
(in fact it's the aim of tests I think).
So now, there ain't crossing
any more, in LaggeredTree.
Tell me what kind of new layout you wish to
see in Roassal, maybe you can have a look at D3 library.
Very impressive library. A lot to live up to. As a bystander, here are
a few that I liked:
http://mbostock.github.io/d3/talk/20111116/force-collapsible.html
http://bl.ocks.org/mbostock/4063550
http://mbostock.github.io/d3/talk/20111018/cluster.html
cheers -ben
Or maybe I
will start looking at how to increase roassal scalability.
Just tell
Regards
Mathieu
6:38 p.m.
On May 6, 2013, at 5:03 PM, Ben Coman <btc(a)openInWorld.com> wrote:
mathieubmddehouck(a)mailoo.org wrote:
this one shows that roassal can be stil optimized.
mathieu
worked on that one.
this one is interesting.
I think that having more variation in trees would be good.
And the sugiyama algorithm too to minimize crossing.
stef
Hi
I've made kind a big refactoring in Roassal-Algorithm, as I've
learnt that ROContainer's attributes was there for any kind of use, now
the CompactTree family uses it, there are new methods for ROElement in
the package, but no more need of ROCompactTreeNode (former RONode).
In
the same time, I've written tests to be sure that the code still works
(in fact it's the aim of tests I think).
So now, there ain't crossing
any more, in LaggeredTree.
Tell me what kind of new layout you wish to
see in Roassal, maybe you can have a look at D3 library.
Very impressive library. A lot to live up to. As a bystander, here are a few that I
liked:
http://mbostock.github.io/d3/talk/20111116/force-collapsible.html
cheers -ben
Or maybe I
will start looking at how to increase roassal scalability.
Just tell
Regards
Mathieu
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
9:11 p.m.
Very
impressive library. A lot to live up to. As a bystander, here are a few that I liked:
http://mbostock.github.io/d3/talk/20111116/force-collapsible.html
this one shows that roassal can be stil optimized. mathieu worked on that one.
this one is interesting.
Yes. Although I would not focus on rotating the text. Roassal gives more interaction
mechanism than D3 (from what I can see in the demo). Getting sexy way to get the name of
nodes is not complex.
I think that having more variation in trees would be good.
And the sugiyama algorithm too to minimize crossing.
Roassal has the Sugiyama algorithm.
Alexandre
stef
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
cheers -ben
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Or maybe I
will start looking at how to increase roassal scalability.
Just tell
Regards
Mathieu
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
8 May
8 May
10:30 a.m.
this one is interesting.
Yes. Although I would not focus on rotating the text. Roassal gives more interaction mechanism than D3 (from
what I can see in the demo). Getting sexy way to get the name of nodes is not complex.
Yes because they did not think about it yet.
And I hope that they will not.
My point is that we have resources now so let us them because in 2 years from now I have
no idea how the situation will be
I think that
having more variation in trees would be good.
And the sugiyama algorithm too to minimize crossing.
Roassal has the Sugiyama algorithm.
Alexandre
stef
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
cheers -ben
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Or maybe I
will start looking at how to increase roassal scalability.
Just tell
Regards
Mathieu
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
9:58 p.m.
Yes. Although
I would not focus on rotating the text.
Why because with athens now we can do it for real. Roassal gives
more interaction mechanism than D3 (from what I can see in the demo). Getting sexy way to
get the name of nodes is not complex.
Yes because they did not think about it yet.
And I hope that they will not.
My point is that we have resources now so let us them because in 2 years from now I have
no idea how the situation will be I think
that having more variation in trees would be good.
And the sugiyama algorithm too to minimize crossing.
Roassal has the Sugiyama algorithm.
Alexandre
stef
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
cheers -ben
> Or maybe I
> will start looking at how to increase roassal scalability.
> Just tell
>
>
> Regards
> Mathieu
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
6 May
6 May
6:21 p.m.
Mathieu for the scalability you should talk to igor because he has some ideas.
Stef
Hi
I've made kind a big refactoring in Roassal-Algorithm, as I've learnt that
ROContainer's attributes was there for any kind of use, now the CompactTree family
uses it, there are new methods for ROElement in the package, but no more need of
ROCompactTreeNode (former RONode).
In the same time, I've written tests to be sure that the code still works (in fact
it's the aim of tests I think).
So now, there ain't crossing any more, in LaggeredTree.
Tell me what kind of new layout you wish to see in Roassal, maybe you can have a look at
D3 library.
Or maybe I will start looking at how to increase roassal scalability.
Just tell
Regards
Mathieu
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
4246
days inactive
4248
days old
7 comments
4 participants
participants (4)
-
Alexandre Bergel -
Ben Coman -
mathieubmddehouck＠mailoo.org -
stephane ducasse