FAMIX support for generics
by Alexandre Bergel
Hi!
What would be the nice way to represent a generic type in Famix?
It seems to me that subclassing FAMIXAbstractScopable into a
FAMIXGenericType is the way to go.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
15 years, 4 months
Referencing absent classes
by Alexandre Bergel
Dear List,
Let's imagine that a class B is imported into a FAMIX Model, and A,
the superclass of B, has _not_ been imported. Should the superclass
of the B FAMIXClass refers to a FAMIXUnknownVariable?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
15 years, 5 months
About importing a model from a stream.
by stéphane ducasse
Hi
I wanted to import a model from a stream
I did the following:
m := SCG.Moose.MooseModel new.
loader SCG.Moose.MooseImporter withActiveMetamodel.
loader importSTream: NameMatchingTest lanModel readStream.
Now I do not know how I can specify in which model the resulting
entities should be added.
When I use an SmalltalkImporter I usually do it that way:
m := SCG.Moose.MooseModel new.
PundleImporter new
model: m ;
addPundleNamed: 'xxx' ;
run
and m is populated.
So Importer is not following the same pattern or I'm stupid and in
both cases this is annoying.
stef
15 years, 5 months
About deprecated
by stéphane ducasse
Hi
I saw that name: is depreacted in moose model. However it does not
give me any hints of the solution.
It would be nice to use the deprecated method to help the reader to
understand what is the alternative.
stef
15 years, 5 months
Fwd: [vwnc] Did RBParser changed in 7.6
by stéphane ducasse
:)
Apparently this is the problem.
Stef
Begin forwarded message:
> From: Stefan Schmiedl <s(a)xss.de>
> Date: April 21, 2008 11:50:25 PM CEDT
> To: vwnc(a)cs.uiuc.edu
> Subject: Re: [vwnc] Did RBParser changed in 7.6
>
> Hi Stef,
>
> that's my bug, I saw it first :-)
>
> On Mon, 21 Apr 2008 22:36:01 +0200
> stéphane ducasse <ducasse(a)iam.unibe.ch> wrote:
>
>> Then the bug is fishy because we get a NonBoolean receiver but when I
>> inspect and executed each of the statement
>>
>> of
>>
>> patchLiteralArrayToken
>> (self patchLiteralArrayEmbeddedAssignmentToken
>> or:
>> [self patchLiteralArraySpecialToken
>> or:
>> [self patchLiteralArrayDottedNameToken
>> ifFalse: [self patchLiteralArraySymbolToken ]]])
>> ifFalse:
>> [^self parserError: #InvalidToken << #browser >> 'Invalid token']
>>
>> I get booleans.
>> and patchLiteralArraySymbolToken is returning boolean.
>
> The problem is one line above: #patchLiteralArrayDottedNameToken
> might return true, and 'true ifFalse: [0]' evaluates to nil.
> There is an AR open for this already, #54201 or #54202.
>
> s.
> _______________________________________________
> vwnc mailing list
> vwnc(a)cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>
15 years, 5 months
this is strange
by stéphane ducasse
This is strange
I'm loading in ***7.5*** the following
self loadingSpecs: #(#(PKG '1.13' 'VisualWorksFoo' '')
#(#PKG '38b.kuhn.2' 'SUnitToo' '')
#(#PKG '33.tgriggs' 'ExtraRBForSUnitToo' '')
#(#PKG '7.4.kuhn.3' 'AutoComplete' '')
#(#PKG '1.1' 'RBrowserHistory' '')
#(#PKG '66' 'RBCodeHighlighting' #setColors)
#(#PKG '1.2' 'RB_Tabs' '')
#(#PKG '1.45' 'MagicKeys' '')
#(#PAR '' 'RBSUnitExtensions' '')
#(#PKG '1.0' 'Tools-Speed patches' '')
#(#PKG '1.1' 'Store-Speed patches' '')
#(#PKG '1.0' 'Store-LogginSpeedUp' ''))
and I get an error SUnitToo(ls) (RB4xx - 27, triggs)
I do not understand why when I load old packages with the old 7.5
version I get errors.
Did someone change something?
Am I getting stupid?
Stef
15 years, 5 months
Fwd: [Moose] Importing Moose bundle crash in 7.6
by Tudor Girba
Begin forwarded message:
> From: stephane ducasse <stephane.ducasse(a)free.fr>
>
> Hi
>
> if you try to load moose development bundle in 7.6 (just loading
> moose)
> crashes in patchLiteralArrayToken.
>
> Apparently when parsing
>
> Text for 'modelVersion3
> ^
> #(Moose.Model (entity
> (FAMIX.Namespace (id: 1) (name aNamespace))
>
> (FAMIX.Class (id: 2) (name ClassA) (belongsTo (idref: 1)) (packagedIn
> (idref: 201)))
> (FAMIX.Method (name methodA1) (signature ''methodA1()'') (belongsTo
> (idref: 2)) (LOC 4))
> (FAMIX.Method (name methodA2) (signature ''methodA2()'') (belongsTo
> (idref: 2)) (LOC 5))
> (FAMIX.Attribute (name attributeA1) (belongsTo (idref: 2)))
> (FAMIX.Attribute (name attributeA2) (belongsTo (idref: 2)))
>
> (FAMIX.Class (id: 3) (name ClassB) (belongsTo (idref: 1)) (packagedIn
> (idref: 201)))
> (FAMIX.Attribute (name attributeB1) (belongsTo (idref: 3)))
>
> (FAMIX.InheritanceDefinition (subclass (idref: 3)) (superclass
> (idref: 2)))
>
> (FAMIX.Class (id: 4) (name ClassC) (belongsTo (idref: 1)) (packagedIn
> (idref: 202)))
> (FAMIX.Method (name methodC1) (signature ''methodC1()'') (belongsTo
> (idref: 4)) (LOC 4))
> (FAMIX.Method (name methodC2) (signature ''methodC2()'') (belongsTo
> (idref: 4)) (LOC 10))
> (FAMIX.Method (name methodC3) (signature ''methodC3()'') (belongsTo
> (idref: 4)) (LOC 7))
> (FAMIX.Attribute (name attributeC1) (belongsTo (idref: 4)))
> (FAMIX.Attribute (name attributeC2) (belongsTo (idref: 4)))
>
> (FAMIX.InheritanceDefinition (subclass (idref: 4)) (superclass
> (idref: 2)))
>
> (FAMIX.Class (id: 5) (name ClassD) (belongsTo (idref: 1)) (packagedIn
> (idref: 202)))
> (FAMIX.Method (name methodD1) (signature ''methodD1()'') (belongsTo
> (idref: 5)) (LOC 3))
>
> (FAMIX.InheritanceDefinition (subclass (idref: 5)) (superclass
> (idref: 4)))
>
> (FAMIX.Package (id: 201) (name aPackage))
> (FAMIX.Package (id: 202) (name anotherPackage))
> ))'
> _______________________________________________
> Moose mailing list
> Moose(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Every now and then stop and ask yourself if the war you're fighting
is the right one."
15 years, 5 months
moose configuration
by Tudor Girba
Hi,
To know how up to date the Moose Config from your image is, you now
can spawn a Mondrian visualization from Tools/Moose Utilities/Moose
configuration.
The visualization will show all the prerequisite packages/bundles of
Moose Config.
Red means there are newer versions in Store, and blue means the local
package is changed.
Cheers,
Doru
--
www.tudorgirba.com
www.tudorgirba.com/blog
"We cannot reach the flow of things unless we let go."
15 years, 5 months
Colored nodes
by Alexandre Bergel
Dear list,
I wish to color some nodes according using a metric. Ideally, I would
love to use something like:
view nodes: each classes forEach: [:node| node setColor: (...)].
But setColor:, color: are not defined on Mondrian.NodeFigure.
Each node may potentially have a different color.
I tried to use "view node: ... forIt: ..." and "view nodes:
aCollection using: aShape " but this was not successful.
I found a way to color all nodes contained in a view with:
-=-=-=-=-=-=-=-=-=-=-=-=
view nodes: packages forEach: [:each |
view blueRectangleShape.
view nodes: each classes.
view gridLayout.].
-=-=-=-=-=-=-=-=-=-=-=-=
i am nearly there :-)
Any help?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
15 years, 5 months
Setup and VW version
by Tudor Girba
Hi,
Because we had all sorts of problems with the Setup scripts in 7.6, I
extended the Setup package to also deal with the VW version.
So, now in your setup method you should both add the <user: yourname>
pragma and the <vwVersion: '7.x'> pragma.
I went over the existing setups and added the correct vwVersion: to
all setups. Please check if it works for you.
Cheers,
Doru
--
www.tudorgirba.com
www.tudorgirba.com/blog
"There are no old things, there are only old ways of looking at them."
15 years, 5 months
