I have exactly the same effect with any namespace I import (for namespaces imported as side-info as well as namespace which I am importing). It would be nicer if they would actually be nested since one of the clustering algorithms uses the recursiveClasses (which currently gives back exactly the same as classes), and which would automatically be nested in the cluster browser...
Reproducing just comes down to loading whatever namespace which has subnamespaces (SCG?) and inspecting it :)
Toon
On (18/07/07 09:15), Adrian Kuhn wrote:
From: Adrian Kuhn akuhn@gmx.ch To: sellossa@ensieta.fr Cc: Moose-dev Bugs moose-dev@iam.unibe.ch Subject: [Moose-dev] Re: MooseModel and namespaces Date: Wed, 18 Jul 2007 09:15:07 +0200
Hey Sara, please provide a sample mse file, such that we can try to reproduce the bug.
AA
On 17 Jul 2007, at 22:51 , sellossa@ensieta.fr wrote:
Hi!
I have a question concerning the structure of a MooseModel.
Imagine that we have a project with three Namespaces: Namespace A, NamespaceB, NamespaceC. In my project, NamespaceA contains NamespaceB and NamespaceC. Then, I import the project in Moose and I get a MooseModel with my three namespaces.
When I inspect NamespaceB and NamespaceC, I can see (thanks to the attribute 'belongsTo') that they both belong to NamespaceA Nevertheless, when I inspect NamespaceA, I realise that attribute 'namespaces' is an empty OrderedCollection.
Is it normal? Because I think that 'namespaces ' should contain NamespaceB and NamespaceC, isn't it?
thanks
Sara
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