Hello Andreas!
Splitting out a "settings subsystem" from the GUI subsystem will achieve
two things:
1. We can implement settings in a GUI-agnostic way. This is very good.
2. There will be restrictions in what settings are possible. This will
probably not be a practical problem because we can add new means of
doing settings as they are needed.
I don't think this addresses the problem though, because the subsystems
with settings will still have two essential parts (when examining the
dependencies). One part depends only on the Model subsystem(s), and the
other on the "settings subsystem". If they are not split in two, it
means that also the "settings subsystem" will have to be made available
when testing the bulk of the subsystem.
Or am I reading what you write all wrong? Are you suggesting the third
alternative, where all settings of all subsystems are collected in a
huge application subsystem? I think this third alternative feels wrong
because we want to provide a way of plugging in modules (ada, sysml,
...) some of which we wont even know about because they will be
developed and distributed within a closed organization. Since these
modules will provide their settings we will then have a difference
between how the settings of "core" subsystems and "not-core" subsystems
(a module) are dealt with. We don't have crystal clear definition of
subsystems and modules so discussing this is complicated.
/Linus
> -----Original Message-----
> From: Andreas Jerke [mailto:[EMAIL PROTECTED]
> Sent: den 11 februari 2007 02:14
> To: [email protected]
> Subject: Re: [argouml-dev] Subsystems with GUI-parts
>
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
