Ok, one more time.
Take a look at the attached pictures produced with a code like:
view nodes: #(1 2 3) forEach: [:each |
view shape rectangle withText.
view node: each *10].
view shape line color: Color blue; width: 3.
view edgesFromAssociations: {10->30}
In Mondrian, the edge goes below node 20, but above the parent nodes. In Roassal, it goes above node 20.
zOrder is just a mechanism. What you do with it is something else. With Mondrian, we wanted to address people that have little knowledge about how to visualize, and we want to make the defaults as powerful as possible to help them create appealing visualizations.
This is why we use a special zOrder (we did not publish on that, but we should have :)) that basically says that an edge is lower than the least nested linked nodes, but higher than its parents. This is very useful when you have a tone of edges. For example, it is because of this mechanism that the class blueprint is legible even for large classes.
Cheers,
Doru
<zOrder-roassal.png><zOrder-mondrian.png>
On 23 May 2012, at 02:53, Alexandre Bergel wrote:
Regarding zOrder, its usefulness comes when it comes to drawing edges.
Btw, zOrder does not have to be mandatory, but for it to work
efficiently, you need to be able to store this as a property in the
graph element.
I have nothing against a zOrder. I am just trying to see what is exactly the use case for it.
By the way, I did a skype with Dennis, apparently all the problems have been solved.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev