Hi,
I made some progress with the TreeMapLayout. Two challenges remain to be solved. The first one is related to dragging. It is kind if complicated to explain in words, so I made this short screencast:
http://cl.ly/150n1t2Z2h1y3L0z1U0L
As you can see the positions of the shapes get updated only when hovering over them, not instantly when dragging, as I would like them to.
One difference code-wise to other graph layouts is that the owner of all shapes is, in this case, not MORoot but the node "org", which is a normal MONode. I had to do this (change ownership) because MORoot does not get drawn (is this by design?).
Does anyone have some ideas on what could explain this behavior?
Another question would be: Is it possible to make the inner nodes not draggable? The user should not be able to move individual shapes inside the TreeMap around.
Cheers, Dennis
You have a very strange effect when you are dragging nodes. Clearly, this should not happen. How can I try this example on my machine?
MORoot cannot have a shape since there is no thing to render for the root node itself.
Cheers, Alexandre
On 18 Apr 2012, at 03:16, Dennis Schenk wrote:
Hi,
I made some progress with the TreeMapLayout. Two challenges remain to be solved. The first one is related to dragging. It is kind if complicated to explain in words, so I made this short screencast:
http://cl.ly/150n1t2Z2h1y3L0z1U0L
As you can see the positions of the shapes get updated only when hovering over them, not instantly when dragging, as I would like them to.
One difference code-wise to other graph layouts is that the owner of all shapes is, in this case, not MORoot but the node "org", which is a normal MONode. I had to do this (change ownership) because MORoot does not get drawn (is this by design?).
Does anyone have some ideas on what could explain this behavior?
Another question would be: Is it possible to make the inner nodes not draggable? The user should not be able to move individual shapes inside the TreeMap around.
Cheers, Dennis
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Alexandre,
You can try it by downloading the following images: http://ci.moosetechnology.org/job/softwarenaut-latest-dev/
Then in a workspace you can run:
HiGraphTests new openSimpleSampleHierarchy. "This will open a normal tree view, so one can see the structure of the example" HiGraphTests new openSimpleSampleTreeMapMultiple. "This will open a view with all nodes on level 3 of the tree as treemaps" HiGraphTests new openSimpleSampleTreeMap. "This will open the whole tree as treemap"
The difference between the two layouts is that when rendering multiple nodes as treemaps, in the layout *doExecute: aGraph* method, aGraph is a MONode, in the case of rendering only one treemap, it is a MORoot. I am not sure why this is the case. This why I have to handle these two cases separately, which leads to different behavior.
It would be great if you could have a look.
Thanks and Cheers, Dennis
On Thu, Apr 19, 2012 at 15:28, Alexandre Bergel alexandre.bergel@me.comwrote:
You have a very strange effect when you are dragging nodes. Clearly, this should not happen. How can I try this example on my machine?
MORoot cannot have a shape since there is no thing to render for the root node itself.
Cheers, Alexandre
On 18 Apr 2012, at 03:16, Dennis Schenk wrote:
Hi,
I made some progress with the TreeMapLayout. Two challenges remain to be
solved.
The first one is related to dragging. It is kind if complicated to
explain in words, so I made this short screencast:
http://cl.ly/150n1t2Z2h1y3L0z1U0L
As you can see the positions of the shapes get updated only when
hovering over them, not instantly when dragging, as I would like them to.
One difference code-wise to other graph layouts is that the owner of all
shapes is, in this case, not MORoot but the node "org", which is a normal MONode. I had to do this (change ownership) because MORoot does not get drawn (is this by design?).
Does anyone have some ideas on what could explain this behavior?
Another question would be: Is it possible to make the inner nodes not
draggable? The user should not be able to move individual shapes inside the TreeMap around.
Cheers, Dennis
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Dennis,
I checked at the code. The class TreeMapLayoutTests does not have tests. It contains 3 methods that does not seem to do much. Having some unit tests will really help understand how the tree layout works and how to improve it.
I have seen you have added zOrder: on MONode. Is this to remove the edges (i.e., put the nodes in front of the edges)?
Cheers, Alexandre
PS: Sorry for my late reply.
On 25 Apr 2012, at 04:05, Dennis Schenk wrote:
Hi Alexandre,
You can try it by downloading the following images: http://ci.moosetechnology.org/job/softwarenaut-latest-dev/
Then in a workspace you can run:
HiGraphTests new openSimpleSampleHierarchy. "This will open a normal tree view, so one can see the structure of the example" HiGraphTests new openSimpleSampleTreeMapMultiple. "This will open a view with all nodes on level 3 of the tree as treemaps" HiGraphTests new openSimpleSampleTreeMap. "This will open the whole tree as treemap"
The difference between the two layouts is that when rendering multiple nodes as treemaps, in the layout doExecute: aGraph method, aGraph is a MONode, in the case of rendering only one treemap, it is a MORoot. I am not sure why this is the case. This why I have to handle these two cases separately, which leads to different behavior.
It would be great if you could have a look.
Thanks and Cheers, Dennis
On Thu, Apr 19, 2012 at 15:28, Alexandre Bergel alexandre.bergel@me.com wrote: You have a very strange effect when you are dragging nodes. Clearly, this should not happen. How can I try this example on my machine?
MORoot cannot have a shape since there is no thing to render for the root node itself.
Cheers, Alexandre
On 18 Apr 2012, at 03:16, Dennis Schenk wrote:
Hi,
I made some progress with the TreeMapLayout. Two challenges remain to be solved. The first one is related to dragging. It is kind if complicated to explain in words, so I made this short screencast:
http://cl.ly/150n1t2Z2h1y3L0z1U0L
As you can see the positions of the shapes get updated only when hovering over them, not instantly when dragging, as I would like them to.
One difference code-wise to other graph layouts is that the owner of all shapes is, in this case, not MORoot but the node "org", which is a normal MONode. I had to do this (change ownership) because MORoot does not get drawn (is this by design?).
Does anyone have some ideas on what could explain this behavior?
Another question would be: Is it possible to make the inner nodes not draggable? The user should not be able to move individual shapes inside the TreeMap around.
Cheers, Dennis
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Dennis Schenk