Ok, I was completely wrong ;) I have read chapter 4 of the cookbook and understand the meaning of subsystem now... So my idea of removing the small GUI parts only needed for settings is to provide either a new "settings subsystem" or implement the settings view/controller in the application subsystem. Perhaps with a callback interface. > Hello, > > I unfortunately had not much time reading the cookbook or looking at the > argouml code - just my 2 cent: > > > Many of our subsystems have a small GUI part. It could be as small as > > a tab in the Settings-window. > > Perhaps these small parts are "quick hacks" and break the MVC pattern. > The argouml core system needs to provide these subsystems methods for > dealing with the GUI. > > For example: > If a subsystem needs some settings, it should register its own setting > handler etc. with the setting system. > > Subsystems, which provide complete new GUI functionality should be > splitted into two View/Model subsystems. But this should be an > exception! > > Regards, > Andreas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
