Hi!
Just to keep you updated with the excellent work Sergio Maas did with Roassal 2.
Roassal2 now support SVG path. The cool thing about it, is that the web is stuffed with really nice looking icon (e.g., http://iconmonstr.com). We can now embed these icons in any visualization.
As an example, consider this:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| v shape |
v := RTView new.
shape := RTSVGPath new path: 'M442.264,283.033l-90.66,52.343l28.787,16.621c-28.083,38.277-64.824,62.301-104.362,68.397V231.153
c0-54.82,48.786-60.084,48.786-112.339C324.814,80.869,293.944,50,256,50c-37.943,0-68.814,30.869-68.814,68.814
c0,52.694,48.786,57.052,48.786,112.338v189.242c-39.538-6.097-76.278-30.12-104.363-68.397l28.788-16.621l-90.66-52.343v104.686
l27.018-15.6C137.32,429.445,194.595,462,256,462s118.68-32.555,159.246-89.881l27.018,15.6V283.033z M227.242,118.814
c0-15.857,12.9-28.758,28.758-28.758c15.856,0,28.758,12.9,28.758,28.758c0,15.856-12.901,28.757-28.758,28.757
C240.143,147.571,227.242,134.671,227.242,118.814z'.
shape fillColor: Color red.
shape scale: [:vv | vv model ].
v add: ((shape elementsOn: #(0.1 0.2 0.3 0.4) ) @ RTPopup).
v open
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hello,
I use Roassal to visualize a FAST AST as a kind of UML diagram.
Each node on Roassal is a node of the AST and the edges shows the parent
link.
That's work fine and it's very easy to do it ! Thanks !
But I would like to add some text on the edges to know what are the
instance variables containing the children nodes.
I saw the examples and there's not a such functionality.
Is it possible to add it ?
Cheers,
Vincent
The Roassal2 job now sets the author. The builds does not crash anymore,
but there are 11 failing tests.
Here is the new script:
----
wget --quiet -O - http://get.pharo.org/30+vm | bash
./pharo Pharo.image save $JOB_NAME
REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main
./pharo $JOB_NAME.image config $REPO ConfigurationOfRoassal2
--install=development
./pharo $JOB_NAME.image eval "Author fullName: 'Test'. Smalltalk image
saveAs: 'roassal-tests'"
./pharo roassal-tests.image test --junit-xml-output "Roassal2.*|Trachel.*"
mv ./pharo-vm/PharoV20.sources ./
zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources
----
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Updates:
Summary: Roassal should support lazy edges when used through the Mondrian
API
Status:
Labels: -Component-Mondrian Component-Roassal
Comment #10 on issue 113 by tu...(a)tudorgirba.com: Roassal should support
lazy edges when used through the Mondrian API
http://code.google.com/p/moose-technology/issues/detail?id=113
No, it does not. But, it should.
The idea is that the following Mondrian script should work:
view edge: #edge from: 1 to: 2.
view node: 1.
view node: 2.
For this, the edge creation should be evaluated only after all nodes are
created.
I changed the entry title and labels.