Hi Linus, et al.,

IIUC what is written in the cookbook, then the org.argouml.application.configuration is now a package for a "Low Level Subsystem": This since it is used in many places all over ArgoUML, but does not use anything of ArgoUML itself at all. But I do not yet know wich one!

Another example of such package is org.argouml.swingext.
Also, org.argouml.util contains a few classes that belong in a low level subsystem, but not all classes in this package comply.

Maybe I should clarify the definition of a "Low Level Subsystem" according that definition.
It now says:

«
These subsystems are infrastructure subsystems that just are there for every other subsystem to use. They are all insignificant enough not to be mentioned when listing dependencies. All these subsystems are all started and initiated (if needed) from the Application subsystem.
»

This is what I propose:
«
These subsystems are infrastructure subsystems that just are there for every other subsystem to use - but they are not using any other part of ArgUML. They all have a simple dependency structure: All other ArgoUML packages may depend on them, but there are no dependencies "upwards", nor between them. All these subsystems are all started and initiated (if needed) from the Application subsystem.
»

Agreed?

Regards,
Michiel



----- Original Message ----- From: "Linus Tolke" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Saturday, April 21, 2007 5:54 PM
Subject: RE: [argouml-dev] Refactor Configuration to remove cyclic dependency


Hello Michiel!

The questions I would like to have answered is:
* What subsystem do the Configuration and ConfigurationKey belong to?
* Does that subsystem have a dependency loop with some other subsystem?

As I see it the org.argouml.application.api is the remnants of the old
architecture connected to the old plugin system. In the new architecture
we have subsystems. Subsystems have a main package where every
accessible class, api, interface resides. If we can just figure out what
subsystem these things belong to, let's move them to that package
directly instead.

/Linus

-----Original Message-----
From: Michiel van der Wulp [mailto:[EMAIL PROTECTED]
Sent: den 19 april 2007 19:32
To: [email protected]
Subject: [argouml-dev] Refactor Configuration to remove cyclic
dependency

Hi All,

To remove the cyclic dependency between
    org.argouml.application.api and
    org.argouml.application.configuration,
I'd like to move the 2 classes Configuration and ConfigurationKey from
the
former to the latter package.

This means adapting many files, also in many sub-projects of ArgoUML,
since
the Configuration is often used.

Since this is such a large scale change, and involves many
sub-projects of
ArgoUML, I'd like some input. Please react if there are remarks on
this
change!
Without any protest, I will perform this change tomorrow.

Regards,
Michiel

---------------------------------------------------------------------
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]



--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.463 / Virus Database: 269.5.7/771 - Release Date: 21/04/2007 11:56



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to