11 Dec
2008
11 Dec
'08
11:52 p.m.
Hi,
Well, isn't it obvious? :)
Before the typo and the incomplete end of sentence, I meant in fact
MooseModel as a subclass of MooseGroup (for example) - or it could
be that MooseGroup is a subclass of MooseModel. Now it's just a
naive question, I didn't look at the differences between the two.
MooseGroup adds the ability to morph its type based on the elements
inside. MooseModel has other responsibilities. So they are siblings.
In the same time, they both are subclasses of MooseAbstractGroup
because they share the storage mechanism.
More details about MooseGroup:
- It should be subclassed for every group of entities that is of
interest
- The typed groups can then be home for behavior/properties that are
meta-described and that can be seen in the Finder
- Example of a popular Group is ClassGroup which holds FAMIXClasses. A
behavior of this is viewSystemComplexity to view it in Mondrian.
Furthermore, because in viewSystemComplexity you will get some pragma,
you will be able to construct a menu when you select a ClassGroup in
the Finder.
Cheers,
Doru
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Relationships are of two kinds: those we choose and those that
happen. They both matter."
MooseModel - a named group, created only when
importing a project
into Moose. I'm not sure why it is a sibling of MooseGroup and
not, for example, a sibling.
a sibling of ? :)