Moose-dev July 2012

moose-dev@list.inf.unibe.ch

22 participants
110 discussions

migrating to Roassal - custom shapes
by Ben Coman 05 Aug '12

05 Aug '12

Referring to the attached graph, what is the best way to approach the following in Roassal. Currently with Mondrian I produce a produce a custom shape using the forms builder in #mondrianShape, which is a method of my ModelRoot class. Referring to the attached graph, as an example this shows the class name "Substation" above the instance "SS1" and has a space for contained items to be displayed within it. >>mondrianShape | builder | builder := MOFormsBuilder new. builder column; center; fill; pref; grow. builder row; center; pref; fill; grow; row; center; pref; fill; grow; row; center; pref; fill; grow. builder x: 1 y: 1 add: ( MORectangleShape new text: #strippedClassName; textAlignment: #left; borderColor: Color white ) . builder x: 1 y: 2 add: ( MORectangleShape new text: #localName; textAlignment: #left ) . builder x: 1 y: 3 add: ( MORectangleShape new ) . builder x: 1 y: 3 add: ( MOChildrenShape new ) . ^builder shape In conjunction with the use of MOChildrenShape above, class ModelRoot also has method #addSubViewTo: which descends through contained classes - for example instance "primary" inside "T1" inside "SS2" inside "Figure 8..." >>addSubViewTo: aMOViewRenderer aMOViewRenderer node: self using: self mondrianShape forIt: [ self children do: [ :child | child addSubViewTo: aMOViewRenderer. ] ] My initial issues in migrating this to Roassal are: 1. Roassal appears to not provide any methods that have "using:" in them. 2. Roassal appears to not support MOFormsBuilder It may be that I am accessing to much internal methods. The code above was the result of evolutionary hacking as I was learning Mondrian. I would be happy to re-architect if someone can advise best practice for Roassal. cheers -ben

3 5

migrating to roassal - MOArrowedOrthoVerticalLineShape
by Ben Coman 05 Aug '12

05 Aug '12

I am usings the code to produce the attached image. view shape: (MOArrowedOrthoVerticalLineShape new). view edges: inheritance from: #superclass to: #yourself. How do I achieve that with Roassal? And just to document something I got working... previously to hide lines while keeping the layout I was using... view shape: (MOStraightLineShape new color: Color white). view edgesFrom: [ :xx | xx - 1 ]. and now... (view edgesFrom: [ :xx | xx - 1 ] ) do: [ :edge | edge - ROEdge ] . cheers -ben

2 5

Quest for Hierarchical Data
by Mircea Filip Lungu 05 Aug '12

05 Aug '12

Hello Moosers, As you already know, Dennis is working on the hierarchical graph data structure and its great associated visualization in Pharo :) We have been testing his code on software systems which have an inherently hierarchical structure with low level relationships propagating up along the package structure, but also thought we would try it on a different type of hierarchical data. The two contributions (the HG data structure & the visualization) are after all independent of the domain model. Do you know of any data sources that have the following two properties? 1. There exists a set of relationships between low level, leaf entities 2. The low level, leaf entities can be aggregated along containment relationships One example would be trade relationships existent between companies, can be aggregated to regions, countries, continents... If you are aware of such a data set, we'd offer a beer for the information :) Cheers! M.

8 17

MooseChef: to what package do methods belong?
by Nicolas Anquetil 02 Aug '12

02 Aug '12

Another MooseChef decision: aPackage queryOutgoingReferences returns all the FamixReferences made from aPackage. this is implemented by taking all methods (self methods) in the package and asking them what reference they make. And we have FAMIXPackage>>methods ^ self localMethods union: self extensionMethods So when asking a package what external references it makes, we get references stemming from methods that extend classes of other packages. We found this while computing a coupling metric for packages. So the solution would be easy to implement, but we are not sure what is the best solution ? - we could change FAMIXPackage>>methods (methods belong to the package that owns their class) - we could change queryOutgoingReferences (references/invocation/accesses stem from the methods in the classes in the package, not from the methods in the package) - or we could change our metric nicolas

4 7

Issue 822 in moose-technology: Roassal line color does not work with the model of the edge
by moose-technology＠googlecode.com 30 Jul '12

30 Jul '12

Status: New Owner: tudor.gi...(a)gmail.com CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7 New issue 822 by tudor.gi...(a)gmail.com: Roassal line color does not work with the model of the edge http://code.google.com/p/moose-technology/issues/detail?id=822 Right now, the color of a line is a constant. It should be a transformation that works with the model of the edge.

1 2

Issue 821 in moose-technology: Roassal Mondrian builder crashes when an edge has the same model as one of the nodes
by moose-technology＠googlecode.com 29 Jul '12

29 Jul '12

Status: New Owner: tudor.gi...(a)gmail.com CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7 New issue 821 by tudor.gi...(a)gmail.com: Roassal Mondrian builder crashes when an edge has the same model as one of the nodes http://code.google.com/p/moose-technology/issues/detail?id=821 To reproduce after the introduction of models behind edges: view nodes: (Array with: 4 with: 2). view edges: (Array with: 4 with: 2) from: 4 to: 2.

1 1

Issue 820 in moose-technology: Roassal Mondrian builder does not initialize edges with a model
by moose-technology＠googlecode.com 29 Jul '12

29 Jul '12

Status: New Owner: tudor.gi...(a)gmail.com CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7 New issue 820 by tudor.gi...(a)gmail.com: Roassal Mondrian builder does not initialize edges with a model http://code.google.com/p/moose-technology/issues/detail?id=820 The method used for initializing the edge is: buildEdgeFrom: fromNode to: toNode "Shape is not initialized here" ^ (ROEdge from: fromNode to: toNode) + shape The problem here is that the edge does not receive a model object. Because there is no model object, the transformations for properties like width or color cannot be expressed properly.

1 1

Issue 819 in moose-technology: Roassal line width does not work with the model of the edge
by moose-technology＠googlecode.com 29 Jul '12

29 Jul '12

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7 New issue 819 by tudor.gi...(a)gmail.com: Roassal line width does not work with the model of the edge http://code.google.com/p/moose-technology/issues/detail?id=819 This does not work at the moment: view := ROMondrianViewBuilder new. view shape label. view nodes: (1 to: 2). view shape line width: [:x | x ]. view edgesFrom: [:x | x // 2]. view treeLayout . view open

1 1

Issue 818 in moose-technology: Roassal tree layout does not preserve the order of nodes
by moose-technology＠googlecode.com 29 Jul '12

29 Jul '12

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7 New issue 818 by tudor.gi...(a)gmail.com: Roassal tree layout does not preserve the order of nodes http://code.google.com/p/moose-technology/issues/detail?id=818 In Pharo 1.4, Collection>>difference: uses a set, thus, it does not preserve the order of the elements. Because of this, the following method has to be rewritten: ROAbstractGraphLayout>>childrenFor: aNode except: aNodeCollection ^(self childrenFor: aNode) difference: aNodeCollection

1 1

Roassal Easel examples interface
by Ben Coman 29 Jul '12

29 Jul '12

Just a few thoughts about how the Roassal Easel [Examples] are presented. Some text describing the meaning of the blue and pink grouping boxes would be useful - but to hazard a guess blue is the replicated Mondrian functionality and pink is the new Roassal functionality ? The ZoomIn and ZoomOut buttons don't work with either the [Examples] of [Info] displayed - which is fair enough, but there is no feedback to indicate the buttons will have no effect. This is quite nit-picking so perhaps can be ignored. Once any particular example is clicked, there is nothing that displays what the current example is - so if (like me) you forget which it was two seconds after you click it, you end up a bit lost. It would be nice to have something that identifies the current example. Example>interaction>leftAndRightClick - fails Example>interaction>clickAndMove - the element ends up about 150 pixels below the click. It should either centre or align a corner with the click. Example>colors>normalizer - it is not clear what the purpose of this is, especially under a colors section - it is just an empty black box that is moved around.

2 1

← Newer
1
...
5
6
7
8
9
10
11
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2012