I loaded the latest Mondrian packages into Damien 3.10 dev on OSX in this
order
- announcements
- mondrian
- mondrian paintings
Running all 26 tests gave 16 errors.
MOFormsBuilderTest testAdvancedApi sort-of hangs the image (drawing not
displayed until I Alt-. interrupt). I occasionally see MNU for
MOLabelShape>>width
Am I using an incorrect version/combination?
Thanks ~ Sophie
Hi doru
I would like to know what is the status of isStub in Famix30?
I'm trying to get that working in FAMIX30
I have
FAMIXEntity stub: aBoolean
self isStub: aBoolean
and isStub: is defined only on and EntityState
FAMIXNamedEntity isStub: aBoolean
isStub := aBoolean
Then in
MinimalState isStub: boolean
[boolean == false] assert
I imagine that the code above is only used when there is no property
EntityState isStub: boolean
^self attributeSet: #privateIsStub value: boolean
Sorry if this is a repeat, not sure if my first post came through.
Is it possible with Mondrian to do any of the following:
- generate labels on graph edges e.g. names of association ends in a UML
class diagram?
- generate nodes like class nodes (with name, line, attributes list, etc.)?
- possibly with some layout coding, generate component-port-connector
models: labeled boxes, labeled lines between boxes, labeled mini-boxes on
the edges of the connections
- Are these reasonable usages of current Mondrian capability?
Thanks!
Hi doru
right now isAbstract and isPublic are in the Famix-Smalltalk and I
think that they should be in core.
After we could have isPackageProtected for Java in Famix-Java.
Stef
Is it possible with Mondrian to generate labels on graph edges e.g. names of
association ends in a UML class diagram? And to generate
nodes like class nodes (with name, line, attributes list, etc.)? Are these
reasonable usages of Mondrian?
Thanks!
Hi guys
in Famix30 we would like to have the isStub property to false.
Since marking as a stub is really something that we do on purpose when
for example
an access does not find the instance variable it should get.
Tell me what us think.
Stef and Jannik
I suppose that the following list of pragmas means that I have a
collection of behavior entities
Is is correct?
<MSEProperty: #candidates type: #FAMIXBehaviouralEntity opposite:
#incomingInvocations> <multivalued>
Now it means that I cannot interpret the first pragma in isolation?
I not sure I like that design
Stef
Hi
I would like to know (may be it would be good to have a FAMIX30
document even a draft)
- because this is really frsutrating to work on FAMIX30 in the dark -
what is the mapping between
FAMIX2Invocation and FAMIX3Invocation
in invokes -> signature
Stef
