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 :)
On (18/07/07 09:15), Adrian Kuhn wrote:
From: Adrian Kuhn <akuhn(a)gmx.ch>
Cc: Moose-dev Bugs <moose-dev(a)iam.unibe.ch>
Subject: [Moose-dev] Re: MooseModel and namespaces
Date: Wed, 18 Jul 2007 09:15:07 +0200
please provide a sample mse file, such that we can try to reproduce
On 17 Jul 2007, at 22:51 , sellossa(a)ensieta.fr wrote:
> 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
> Then, I import the project in Moose and I get a MooseModel with my
> 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
> and NamespaceC, isn't it?
> Moose-dev mailing list
Moose-dev mailing list