|
osdir.com mailing list archive |
|
Subject: Re: [argouml-dev] Subsystems with GUI-parts - msg#00059List: db.axion.develI 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 Thread at a glance:
Previous Message by Date: click to view message previewRE: [argouml-dev] Subsystems with GUI-partsA practical comment... Bob Tarling wrote: > > I don't see any important difference between your model and the > > subsystems that we have explained in the Cookbook (or actually a single > > one but that is connected to the other discussion). > > That's good, the less we need to change there the better. I want the common goal to be defined in the Cookbook. It is to be documented there and all discussions should be based on that description. It cannot, for practical reasons, be based on some common knowledge of what we have agreed, nor on some models or diagrams that you cannot find anymore. We must work with improving the descriptions in the Cookbook as we improve our understanding of our common goal. If you don't agree on what is described in the Cookbook, work with developing and getting everyone to accept the changes! Avoid starting from scratch. That just causes confusion. /Linus Next Message by Date: click to view message previewRe: [argouml-dev] Subsystems with GUI-partsOk, 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: dev-unsubscribe@xxxxxxxxxxxxxxxxxx > For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx Previous Message by Thread: click to view message previewRe: [argouml-dev] Subsystems - the other discussionWe have no target timeframe for UML 2.x migration. We haven't finished the UML 1.3 -> 1.4 upgrade yet. Why not focus on things we can persue effectively until we see someone make actual progress on a UML 2.x toolkit we can use? All my comments are based on how I think things should be architected when they are done. For me, now, I will not have time to do this. I must get my head back to the undo mechanism both in GEF and in ArgoUML that will take a lot of time and effort. Also I'm considering suggesting a student task to reimplement sequence diagrams for GSOC. Any more than this and the occasional bug fix and tidy up I think I'll be stretched too far. It's a long time since I looked at the DI model. There'll be a fair learning curve there I should think. Bob. Next Message by Thread: click to view message previewRe: [argouml-dev] Subsystems with GUI-partsOk, 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: dev-unsubscribe@xxxxxxxxxxxxxxxxxx > For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx Loading Comments...
|
|
