On 11 déc. 08, at 23:26, Tudor Girba wrote:
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 :).
Yeah sorry, my main topic is indeed SqMoose.
> 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
> MooseAbstractGroup - abstract composite
> 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
ok, I will delve into VW to get a better picture.
> 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 ? :)
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.
> 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
ok well, let's keep this discussion for a future (soon to be)
"Every now and then stop and ask yourself if the war you're fighting
is the right one."
Moose-dev mailing list