11 Dec
2008
11 Dec
'08
11:26 p.m.
Hi,
To avoid confusion, please specify from now on whether you are talking
about VW or Squeak. From the names used, I guess in this mail you talk
about Squeak :).
MooseElement - not sure why it is not merged with
MooseEntity
MooseElement is a kind of an Interface. The difference between
MooseElement and AbstractEntity is that MooseElement has no state.
MooseEntity - described as the base class for any
entity
Yep.
MooseAbstractGroup - abstract composite
Yep
MooseGroup - my guess, a group of common entities like
'all
packages', 'methods from selected class'. Comment says 'Group adds
on top the ability to change the type of a group when we add more
items inside', which is not clear to me
In VW there is a GroupTest>>testGroupType that shows the wanted
behavior. Basically, if you add methods in a group and there is a
MethodGroup subcalss of MooseGroup, then you should get an instance of
MethodGroup.
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 ? :)
Now I am not sure how this model is handled through
the moose
finder. Any details to share?
Moose Finder has not much to do with these, as it should work with any
objects.
Cheers,
Doru
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Every now and then stop and ask yourself if the war you're fighting
is the right one."