On 16/02/07, Michiel van der Wulp <[EMAIL PROTECTED]> wrote:
Hi All,
> Ok, my thoughts had been something more like this as I knew there was
> some feature specific code around -
>
> FigCompartment<|----FigEditableCompartment<|----FigFeaturesCompartment
> FigCompartment<|----FigEditableCompartment<|----FigEnumLiteralCompartment
Well, now it is:
FigCompartment<|----FigEditableCompartment<|----FigAttributesCompartment
FigCompartment<|----FigEditableCompartment<|----FigOperationsCompartment
FigCompartment<|----FigEditableCompartment<|----FigEnumLiteralCompartment
Since there is no common code between FigAttributesCompartment and
FigOperationsCompartment, so there was no point in creating an abstract
FigFeaturesCompartment, except to be consistent with the UML metamodel.
Feel free to improve!
I'm already happy with your explanation
BTW: Since Tom's very recent changes, the FigOperationsCompartment is also
used for Receptions - so, maybe we need more refactoring.
As the spec states that receptions appear in the operations
compartment I think we're okay to leave the descriptions as is.
Bob.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
