[Moose-dev] Re: Migration of the Customizable System Complexity view

Send applyLayout to the builder. builder := RTMondrianViewBuilder new. builder nodes: …. builder applyLayout -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Apr 17, 2014, at 1:03 PM, Anne Etien <anne.etien(a)univ-lille1.fr> wrote: layout is not taken into account, so all the elements appear in the center. It seems according to Leo that RTMondrianViewBuilder>>open is not called and so the applyLayout method is never called. wrote: still a construction site :) wrote: viewSimpleSystemComplexityWithSelection: height: width: color: on: to apply on RTMondrianBuilder and no more on an RTView. But it really seems that GLMRoassal2Presentation is waiting for an RTView as view and not a RTMondrianViewBuilder. The elements method does not exist on a RTMondrianViewBuilder. RTMondrianViewBuilder in the Customizable System Complexity view since it has repercussions on Glamour. asGlamorousMultiValue, entity asGlamorousMultiValue, asGlamorousMultiValue ). selection: each model ]] ]. :presentation | OrderedCollection new anne.etien(a)univ-lille1.fr> wrote: that it is not possible. want to modify the initialize method of GLMRoassal2Presentation. System Complexity to use RTMondrianViewBuilder. MooseCustomizableSystemComplexityBrowser>>complexityIn: a :presentation | OrderedCollection new metaphor of the builder. For example, the MondrianBuilder is made for a graph visualization like System Complexity. But, if you would want to visualize a graph that places a lot of emphasis on position and animation, it is probably easier to work with RTView. anne.etien(a)univ-lille1.fr> wrote: the MondrianBuilder. By the way, does it means that normally, the RTView should not be directly manipulated for a visualization, but only builder? works directly with the RTView. This is where the issue comes from :). We should change it to work with the MondrianBuilder. alexandre.bergel(a)me.com> wrote: image. I have created a couple of weeks ago a RTBoundedShapeBuilder. Mondrian uses it. wrote: while right clicking on a group of classes, then visualize and then the fourth item. I made a screenshot to explain and another showing the visu on a MooseModel. I didn't know this visu before Friday, but it is I think a great one ;o) MooseCustomizableSystemComplexityBrowser>>complexityIn: method. Roassal to Roassal2. it in a nice way. For example, with GraphET we often need elements smaller than 5 x 5. anne.etien(a)univ-lille1.fr> wrote: but I think that I shouldn't. Indeed, in Roassal a ROShape had a size of 5@5by default (defaultExtent, I think). In Roassal2, such default size has not been implemented. So I put a patch in the System Complexity View, but I think that it should be done everywhere. Roassal2 as it was in Roassal? When it is done, I will remove my patch. requires a minimum width and height. Could you make it so that it is at least 5? anne.etien(a)univ-lille1.fr> wrote: alexandre.bergel(a)me.com> escribió: anne.etien(a)univ-lille1.fr> wrote: of the Moose Panel from Roassal to Roassal2. popUp. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev