Summary: Roassal should support lazy edges when used through the Mondrian
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
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
I changed the entry title and labels.
I have implemented a Famix-Generator which analyses .NET assemblies and produces mse files for CodeCity as well as the MOOSE platform.
If you want to give it a try, you can download it from my site (german, I am sorry - I will change that in near future):
The generator creates famix artifacts for namespaces, types (classes, interfaces, enums und structs), methods, methods calls and local variables. the tool is not complete (missing features, bugs?), I will enhance it during the next weeks or months.. ;-)
(BTW you need a .NET 4.0 installed on your machine. It does not run on the Mono plattform, right now.)
Labels: Type-Defect Priority-Medium Component-EyeSee
New issue 1013 by usman.bh...(a)gmail.com: Eye line diagrams do not allow
changing line width
Changing lineWidth: block in the example lineDiagram2 does not have an
effect on the line width. To reproduce, have a look on this example:
ESExamples new lineDiagram2
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
Whenever I try to search a text in search dialog, it says message below.
Error: subscript is out of bounds: 8218
 in  in PRFullTextSearch>>visitStructure:
 in Set(Collection)>>anySatisfy:
 in PRFullTextSearch>>visitStructure:
 in BOPortion(PRDecorated)>>acceptDecorated:
Labels: Type-Defect Priority-Medium
New issue 900 by benjamin...(a)gmail.com: Glamour-Roassal should be able to
work with raw ROView not just ROMondrianBuilder
Hopefully, I've cracked this. In response to my own query: "Could
something like a GLMMorphicRoassalRawRenderer be added to the
Glamour-Roassal interface? - which would pass an unencumbered ROView to
the paintingBlock. It is not really a Glamour-Roassal interface at the
moment, more of a Glamour-Mondrian interface."
With the attached slice you can now go...
browser transmit to: #graphic andShow:
[ :a |
newView: [ ROView new @ RODraggable ] ;
painting: [:view :input | view add: ROElement new]
After loading you can first try the new & old tests
then try 'GLMRawRoassalExamplesBrowser open'
I surprised myself that I got this far. A few times I hit a brick wall and
was going to submit a half done proof-of-concept, but then just kept
digging. Apart from hopefully getting integrated, some critical feedback
would appreciated. A few points for review...
1. I had considered using #viewPrototype: with an instance to copy, but
then I wasn't sure how deep I should copy it to produce a new view. So
using a block with newView: seemed the safer path (and it also feels like
it opens up some interesting possibilities, even if I can't think what they
are at the moment)
2. I noticed that GLMRoassalPresentation>>renderOn: had a flag 'This should
be the responsibility of the view'.
This method was one that I previously copied and modified for
GLMRoassalRawPresentation in my "Interactive Roassal" experiment. There I
removed the calls to #applyLayout and #populateMenuOn since these were MNU
for ROView (which had replaced ROMondrianViewBuilder). This time I pushed
these two calls into ROMondrianViewBuilder>>preOpen, where ROView>>preOpen
is left empty. I'm note sure I'm happy with #preOpen as a name but it was
the best I could come up with, since I also refactored
ROMondrianViewBuilder>>open to use it.
3. GLMMorphicRoassalRenderer>>render: had hardcoded reference to #stack
with "ROMorph on: view stack" so I pushed the required difference into
ROMondrianBuilder>>newMorph and ROView>>newMorph.
4. GLMMorphicRoassalRenderer>>actOnPresentationUpdate had hardcoded use of
#stack in "setView: aView stack" so I pushed that into
ROMondrianViewBuilder>>onMorph: and ROView>>onMorph:
5. GLMMorphicRoassalRenderer>>actOnPresentationUpdate had hardcoded
ROMondrianViewBuilder so I modified this to use the block passed to
6. I copied GLMRoassalMorphicTest to GLMRawRoassalMorphicTest with required
7. I copied GLMRoassalExamplesBrowser to GLMRawRoassalExamplesBrowser with
I know some of you are working on DSM-kind of matrix. Oscar has been working on a similarity matrix for Roassal. I just want to share a self-explanble screenshot with you guys.
On this example, the methods of the subclasses of Set are compared between themselves.
Black dot is a couple (m1, m2) that are very similar
More on https://www.facebook.com/media/set/?set=a.550677725018829.1073741833.3405...
Alexandre Bergel http://www.bergel.eu