Hi!
-------- Original-Nachricht --------
> Datum: Fri, 27 Mar 2009 08:53:36 -0400
> Von: Tom Morris <[email protected]>
> An: [email protected]
> Betreff: Re: [argouml-dev] Extend CodeGenerator interface to let module find
> it\'s classes?
--<snip>--
> There are well known methods for doing this without breaking things.
> You need to define a new interface
>
> CodeGenerator2 extends CodeGenerator {
> boolean superSpecialClassFilter();
> }
>
> And then have the caller conditionalize its behavior based on whether
> it's a new-style or old-style module.
>
> But I still think it could be done without changing the API...
Ok, you make my old brain work really hard... :-)
One alternative option would be such a new CodeGenerator2 interface.
I thought about another option. An interface, that filters model elements
(similar to FileFilter).
We would define such an interface and the module developer implements it (or
not).
The CG-dialogue could check then, if a module implements this interface:
if( currentModule instanceof ModelElementFilter) {
for all classes in the selected diagram as currentClass {
if currentModule.wantsToGenerateCodeFor( currentClass) {
select( currentClass)
}
}
:-)
Better?
But I'm not sure if it's worth to create the interface just for this simple
functionality...
Ciao,
Andreas
--
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
http://www.gmx.net/de/go/multimessenger01
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1445451
To unsubscribe from this discussion, e-mail:
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email:
[[email protected]]
