I've always seen a subsystem as being either model or view. Never both.
But nor do I see business functionality split in a one to one relationship between a xyz gui subsystem and xyz business logic subsystem which it looks like you're suggesting. As we only have one physically separated subsystem, the Model Interface that is the only example I can give. It contains no GUI. So I'm not sure why you show a "GUI part of some subsystem". What would the equivelent be of the ModelInterface subsystem? There is no one "GUI part of the model interface". Rather there is an Explorer subsystem (visual) that accesses the model interface and there is a PropPanel subsystem (visual) that accesses the model interface. In fact most GUI subsystem access the model interface. My suggestions in separating out the Notation subsystem is to simply make all that business logic stand alone. That does not mean we now also need a NotationGui subsystem. Any part of the ArgoUML GUI should just be able to call that subsystem whenever it chooses. If you try and keep some gui stuff in each subsystem then I think we'll have a hard time ever removing cyclic dependencies and providing a clean interface. Bob. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
