I am trying to understand how to use the MOForms builder in the following script in the context of a FAMIXClassGroup
view shape rectangle
height: [ :cls | cls numberOfMethods ];
width: [ :cls | cls numberOfAttributes ];
view nodes: self entities forEach: [:each | | builder |
view shape rectangle.
builder := MOFormsBuilder new.
builder column ; fill.
builder row; fill ; row ; fill.
builder x: 1 y: 1 add: MORectangleShape new.
builder x: 1 y: 1 add: (MOLabelShape new text: [ :e | e name ]).
builder x: 1 y: 2 add: (self viewMethodsForClass: each onView: view).
view layout: builder asLayout.
edges: self entities
from: [ :cls | cls superclass ].
where the method #viewMethodsForClass:onView: is as follows:
viewMethodsForClass: class onView: view
view shape rectangle.
^view node: class forIt: [
view shape rectangle.
view nodes: class methods.
What I would like to get is, for each class, a composite figure with
- a label on top
- a composite figure where each subfigure represent a method
Ideally the label and the composite should also be centrally aligned.
However, with my script I get figure attached.
part of AspectMaps is a polymetric view of classes and aspects. For
that I want to use Glamour to specify the metrics for the dimension.
The code below shows what I have (and will embed in another browser at
some point) which leads me to 2 questions and a bug.
First question: how can I let each browser show its title? With 6 of
these it's easy to be confused which is which.
Second question: at some point in the mondrian script I need to
retrieve the selections in each browser. (I dont want to automatically
repaint when a selection is changed). How can I do this?
I have tried to get both of these things to work myself but I'm not
having any success ...
The bug: in the code below add a size: 100 to both column
specifications, and you get a nice ZeroDivide error :-/
| browser mprops cprops aprops|
cprops := #(CLOC NumMeth NumAtt NumJP NumAsp).
aprops := #(ALOC NumPC NumAdv NumJPP).
mprops := #(MLOC MNumJP MNumAsp).
browser := GLMTabulator new.
browser column: [: c | c row: #cheight; row: #aheight; row: #mheight];
column: [: c | c row: #cwidth; row: #awidth; row: #mwidth].
browser showOn: #cheight; using: [
browser tree title: 'Classes Height'; display: cprops.].
browser showOn: #cwidth; using: [
browser tree title: 'Classes Width'; display: cprops.].
browser showOn: #aheight; using: [
browser tree title: 'Aspects Height'; display: aprops.].
browser showOn: #awidth; using: [
browser tree title: 'Aspects Width'; display: aprops.].
browser showOn: #mheight; using: [
browser tree title: 'Methods Height'; display: mprops.].
browser showOn: #mwidth; using: [
browser tree title: 'Methods Width'; display: mprops.].
browser openOn: 'Select'
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Please use the 4.0-beta.4 release of Moose. As it was mentioned in the
announcement mail, this release solves the PrimitiveType problem.
On 4 Jan 2010, at 16:02, Usman Bhatti wrote:
> Hi Doru,
> I have similar problem here. I have generated an MSE file with
> InFusion. Moose (moose-suite-4_0-beta.app) fails to load the file...
> A bit of troubleshooting shows that moose is having a problem with
> PrimitiveType expressions present in mse file. I removed them from
> the generated file and it worked...
> I am sending you the problematic MSE file for bug replication
> On Mon, Jan 4, 2010 at 4:20 PM, Tudor Girba <tudor.girba(a)gmail.com>
> Hi Arif,
> It looks like the MSE that you give as input as an incorrect syntax.
> How did you obtain this MSE?
> On 4 Jan 2010, at 09:49, Arif Iftikhar wrote:
> While loading MSE File in Moose i get the error attached. If i
> proceed it loads 0 entities in moose.Is there any special version of
> moose for such mse file.
> Thanks & Regards
> Arif Iftikhar
> <moose error.JPG>_______________________________________________
> Moose-dev mailing list
> "Value is always contextual."
> Dr. Muhammad Usman Bhatti
> Assistant Professor, FAST-NU LHR
> Office MS-Block
> Ext : 273
"Sometimes the best solution is not the best solution."
I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but
I am getting some problems in its interface so I cannot use it. I also tried
J2Moose but the format generated by the tool is not accepted by moose. Is
there a Java exporter for moose that is compatible with the current MSE file
thanx in advance,
It works fine on my computer. I am also using 7.2.6, but I did not
update the JVM.
On 26 Dec 2009, at 13:04, Simon Denier wrote:
> On 26 déc. 2009, at 12:13, Tudor Girba wrote:
>> Hi Simon,
>> Strange, that should not happen. I would need to see the sources to
>> debug this.
> Here you go. It compiles against Java 6 on Mac Os platform, but I
> didnt install the latest release.
> Also I used infusion 7.2.6
>> On 26 Dec 2009, at 11:49, Simon Denier wrote:
>>> Hi all
>>> I'm trying to generate a mse file for a java project with infusion.
>>> It stops somewhere with this error:
>>> Writing the MSE file for the path: /Users/deniersi/workspace/GecO/
>>> --Export started--
>>> MSE file generation aborted!
>>> which does not give much help.
>>> Last lines in the mse describe beginning of a method
>>> (FAMIX.Method (id: 4318)
>>> (sourceAnchor (ref: 9706))
>>> (parentType (ref: 3))
>>> ref 9706 is '_unknown_path\_unknown_file'
>>> Any idea about how to debug?
>>> Moose-dev mailing list
>> "It's not what we do that matters most, it's how we do it."
>> Moose-dev mailing list
"Be rather willing to give than demanding to get."