Extension Architecture

[Bernhard Reiter]

Am  6. Apr 2005 um 10:13:28 schrieb Jonathan Coles:
> i believe the ExtensionRegistry is the right way to go. i was about to
> write one myself when i noticed that there is already one in UI/.
> however, this class should not be in UI but in Model because extensions
> are a concept which is not specific to the UI but a generic feature of
> thuban. All extensions should be required to register before they can be
> used and the add() method should also take an Extension instance. 

Just a wild guess: It might be in UI, because we had the problem 
to display the registered extensions. And the extensions themselfs
should not depend on UI so they can be automatically tested.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20050406/18ff5e4c/attachment.bin