Thanx for the earlier responses. I think I got my answer. One more thing if
you people can elaborate.
How do we represent system classes.... Do we create Famix.Class entries for
System classes?
thanx once more,
usman
Hi guys
Just that you know with mathieu and hani we are working on an
extension of the smalltalk importer
that merges class and metaclass so it may introduce some problems and
we will fix them.
We are writing new tests, cleaning and deprecated methods around the
importing context, uzw.
Stef
Hello all,
while extracting the inheritance definition of a class, this question poped up
in my mind: how do we specify multiple child classes for a class? Do we create
a new InheritanceDefinition for each one of them, which seems to be the case
with existing MSE files? For example
X <- Y <- A,Z (X is the base class, Y inherits from X, A,Z inherit from Y)
In this case, inheritancedefinition parameter for Y will be (format *Class* for
elaboration)
(FAMIX.InheritanceDefinition
(id: 6)
(superclass (idref: 1 *X*))
(subclass (idref: 3 *A*))
)
(FAMIX.InheritanceDefinition
(id: 7)
(superclass (idref: 1 *X*))
(subclass (idref: 4 *Z*))
)
thanx
Usman
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.
Hi,
when I look at the OMG EMOF spec, I can see Enumeration as a subclass of
DataType.
But it is not implemented in the Meta-EMOF-Model package.hank
Unfortunately, Enums also exits in Ecore model, so I will certainly need
it (as well as EnumLiterals) for my ecore importer.
Do you want I to implement them or do you prefer I assimilate them to
Emof.Type ?
thanks,
BOUAZZA Pierrick
Hi,
I'm facing a dilemma while importing the ecore files : I'm not sure how to
convert the Ecore EDataType.
on the one hand, it can be seen as a classic smalltalk class and converted
in a EMOF.Class but it should creates problem when treating "classic"
class
on the other it can be assimilate to PrimitiveType, but I wonder if
DataType are really "Primitive"
which solution do you think is the best ?
thanks
BOUAZZA Pierrick
New submission from lanza <michele.lanza(a)unisi.ch>:
the name says it all
----------
messages: 94
nosy: lanza
priority: Wish
status: unread
title: Saving histories to mse
________________________________________________
Moose Bugs <moose-dev(a)iam.unibe.ch>
<http://macamis.unibe.ch/trackers/moose/issue70>
________________________________________________
New submission from lanza <michele.lanza(a)unisi.ch>:
i'd like to have the possibility to take an arbitrary group of entities and
transform them into a "model" that I can also export to mse
----------
messages: 92
nosy: lanza
priority: Wish
status: unread
title: transforming groups into models
________________________________________________
Moose Bugs <moose-dev(a)iam.unibe.ch>
<http://macamis.unibe.ch/trackers/moose/issue69>
________________________________________________
New submission from lanza <michele.lanza(a)unisi.ch>:
when the list of models in the moose ui is empty (all models removed) the context
menu does not show up anymore
----------
component: Moose UI
messages: 91
nosy: lanza
priority: Bug
status: unread
title: context menu disappears
________________________________________________
Moose Bugs <moose-dev(a)iam.unibe.ch>
<http://macamis.unibe.ch/trackers/moose/issue68>
________________________________________________
New submission from lanza <michele.lanza(a)unisi.ch>:
It would be good to have a menu item which allows me to select a set of models and
"strip them", i.e., only the model entities should remain without stubs
----------
component: Moose
messages: 90
nosy: lanza
priority: Wish
status: unread
title: Stripping Models
________________________________________________
Moose Bugs <moose-dev(a)iam.unibe.ch>
<http://macamis.unibe.ch/trackers/moose/issue67>
________________________________________________
