That is right and wrong :)
System is the container for the meta-layers, however there is only ONE meta-model and ONE meta-meta-model.
I can understand that we have only one MMModel but I do not understand why I cannot have different MModel.
It seems completely hopeless then that we continue to work on importing EMF metamodels in Moose. Should I really say to sara and pierrick to stop? Still I do not understand why I could not have different models for example FAMIX and Mushroom.
Currently there is no notion of multiple "models", "packages" or "package-import" on the meta-layers.
I do not need model import right now.
There is an EMOF::Package yes, but it is currently abused as a namespace rather than as a package. Nice would be to mirror VW's package/namespace orthogonality also in EMOF.
I do not really understand what you mean. For now I do not need a different namespace.
The point for now is that we just need a kind of repository where we could get the different metaModels:
MetaModelRepository default modelNamed: #Famix MetaModelRepository default modelNamed: #Mushrooms
But that is not planned for the future, because I could not convince Doru of such a solution.
So then there is no point to load MModel in Moose then.
Stef
AA
On 17 Jul 2007, at 20:24 , sellossa@ensieta.fr wrote:
hello
Pierrick has found where the meta models and the meta meta models are loaded. They are in the Class System. To get the meta models, do: System reference metamodel. To get the meta meta modles do: System reference metaMetamodel
sara
Hi
how do I know which are the metamodels that are loaded in visualworks? Is there a repository for metamodels? I thought marc stetller implemented one but it was never up to the point to be integrated in Moose.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev