Without Kontraktor: -=-=-=-=-=-=-=-=-=-= | rawView view | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. view shape rectangle withText. view nodes: Collection withAllSubclasses. view edgesFrom: #superclass. view treeLayout. view open -=-=-=-=-=-=-=-=-=-= With Kontraktor: -=-=-=-=-=-=-=-=-=-= | rawView view k | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. k := MalKontractor toSize: 10. view shape rectangle withText: [:cls | k reduce: cls name ]. view nodes: Collection withAllSubclasses. view edgesFrom: #superclass. view treeLayout. view open -=-=-=-=-=-=-=-=-=-=

On Dec 7, 2013, at 6:50 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: I guess somehow. Now can I use that in the roassal easel/. Can I mix that with mondrian script?

Why not? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Dec 7, 2013, at 2:57 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote:

Ok but my script (which does not work is view shape rectangle size: [:each | each classes size * 5 ]. view shape withCenteredText: [:each | (MalKontractor reduce: each name upTo: 8) ]. view nodes: packageGroup. view gridLayout how do I turn that in roassal. Where can I find an example? Is there a roassal easel? or is the roassal easel bot for mondrian and roassal?

thanks yuri Now I would like the shape not to be influenced by the text. So far I have the impression that I should spend a month or two to build my own tools and this depressed me so much…. Stef On Dec 7, 2013, at 7:23 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:

On Dec 7, 2013, at 7:41 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: It looks a bit well….. from another age. I do not see why we would need hotdraw to do anything. May be michele should have a look at what we have under to trunk. I'm not bashing roassal. I'm saying that Moose does not exploit it well (and that roassal should provide way to cut symbol). the problem is different and have nothing to do with the framwork but more to the use of the framework. - first having a real visualisation with menu proposing semantics action like delete, select connected, mark,,, would make a huge difference. - second, really using the tools for a real scenario will show that we have 95% but the last 5% are like the labels missing the shrinking label in the distribution map. the difference is that when adrian and doru implemented distribution map the first time, they spent attention to the details now we can do a dsitributino in roassal but it was lacking the care to the little details like the shrinking of the labels. Look for example at the metaBrowser. in four methods you have it and it is cool. So I imagine that if someone would spend a bit of time really improving the default visualziations then we would get something really cool. Now everybody focuses on his little papers and we get the wonderful 4 lines scripts visualisation. Stef

view shape withoutBorder. view nodes: packageGroup forEach: [ :pak | view shape label text: [:p | (MalKontractor toSize: 4) reduce: p name ] . view interaction forward. view node: pak. view shape rectangle size: pak numberOfClasses. view interaction forward. view node: pak. view verticalLineLayout. ]. view gridLayout. Alexandre

Why it does not work? Turning it into roassal will be much longer. Why do you want to have pure Roassal? Do you need to do interaction with the visualization? You can send rawView to the view Alexandre