12 Jul
2007
12 Jul
'07
2:31 p.m.
Thanks for reporting, Sara, that is really strange!
What I suppose is that the bug is due to the current solution for
collective behavior. Currently any menu item related to a group of
elements is stored in a helper class, and the link from that elements
of the group to that helper class is done "manually" somewhere in
Moose.Group - maybe you can fix it there, but I dare the link is a
kind of string concatenation with non-full-qualified names and thus
your Whatever::Class is treated the same way as a Famix::Class.
I can have a look next week, when back from holidays,
cheers,
AA
On 12 Jul 2007, at 12:27 , sellossa(a)ensieta.fr wrote:
hi!
I have a question concerning the Moose browser.
As you know, I managed to import models conformed to a personnal
metamodel
in Moose ( my personnal metamodel is not FAMIX). In myn metamodel, I
decided to define my own entities Class, Attibute and Method.
When I imported my models (that contains my personnal classes, my
personnal attibutes and personnal methods) in Moose, something wrong
annoyed me:
when I selected "all classes" in the browser, Moose gave me the
possibility to generate Mondrian views as BluePrintComplexity,
MethodInvocations and so on... Of course, since my entities are not
conformed to FAMIX, the visualisation cannot be applied to my model
(they
lead into a bug except from UML diagrams that work very well :) )
So, here is my question:
I don't understand why Moose proposes Mondrian visualisations
(such as
BlueprintComplexity, Duplcation complexity, Method invocation ans
so on)
to my personnal classes knowing that they are not conformed to the
Famix
meta model. Where can I fix it? I had a look on MooseUI package but I
didn't find what I wanted :(
I hope that my question was clear:)
thank you for your help
sara
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev