Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

migrating to roassal - MOArrowedOrthoVerticalLineShape

by Ben Coman

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

12 years, 11 months

Quest for Hierarchical Data

by Mircea Filip Lungu

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.

12 years, 11 months

Roassal nested edges

by Ben Coman

Just interested in learning more about the internals of Roassal. I see this comment in ROElement>>positionRelativeTo: anElement "Return the position of myself against the position of one of my parent, anElement. The returned position is relative to it." "This method is useful to draw edges that are nested" How do nested edges fit into the architecture ?

12 years, 11 months

Video about importing Java code in Spanish

by Alexandre Bergel

Hi! Some of my students got enthusiast by Moose. One of them did a really cool video: http://www.youtube.com/watch?v=iCd3AtCNAqw&feature=youtu.be Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 11 months

MooseChef: to what package do methods belong?

by Nicolas Anquetil

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

12 years, 11 months

Trouble with Eyesee

by Lautaro Maximiliano pecile

Hi! I am a newbie in Smalltalk and specially en Eyesee. I'm having trouble with the scale of the Y axis in a vertical bar diagram. If I define a dictionary as d := {'a'->(1/3) . 'b'->(3/2) . 'c'->(7/4)}. I can create a nice diagram with this chart := ESDiagramRenderer new. chart verticalBarDiagram y: [:eachAssociation | eachAssociation value]; identifier: [:eachAssociation | eachAssociation key]; regularAxis; models: d . chart open whose Y axis is very well populated with labels indicating different steps in the scale. But if I redefine d as d := {'a'->(1/3) . 'b'->(7/5) . 'c'->(17/4)}. (which is closer to the data I am working on) most of the labels in the Y axis are gone. How can I instruct Eyesee to show a more informative scale? Thanks in advance for your help. Cheers Lautaro Pecile.

12 years, 11 months

The Internet Map

by Andre Hora

Nice visualization: http://internet-map.net -- Andre Hora

12 years, 11 months

Issue 822 in moose-technology: Roassal line color does not work with the model of the edge

by moose-technology＠googlecode.com

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.

12 years, 11 months

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

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.

12 years, 11 months

Issue 820 in moose-technology: Roassal Mondrian builder does not initialize edges with a model

by moose-technology＠googlecode.com

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.

12 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev