Hi Thomas,

Thanks for the update on this.  I'll have a look to see if your changes give
me enough guidance to clean up the other core code generation modules.

One change that we may need to revert is the removal of the Generator2
class.  The C++, C#, & PHP code generation modules all depend on it, so I
wouldn't be surprised if there are 3rd party code generators which do as
well.  It's been deprecated for a while, but since we never really provided
clear guidance to module writers on how to update their modules, I'm not
sure whether we should consider the deprecation clock as starting back then
or just now.

The reason I raised this whole issue in the first place was that I was
trying to redesign the code generation API to make it UI independent so it
could be used with Eclipse.  I'll revisit that now to see what additional
changes need to be made.  If we're going to make significant updates to all
the code generator modules, we might as well get it all done right.

I'll send more after I've had a look at your changes in more detail.

Tom
> -----Original Message-----
> From: Thomas N. [mailto:[EMAIL PROTECTED] 
> Sent: Saturday, October 21, 2006 2:39 PM
> To: [email protected]
> Subject: [argouml-dev] Generator2 [was: What replaces 
> PluggableImport and Generator2? (and other language module questions)]
> 
> 
> Hi Tom,
> 
> regarding Generator2: GeneratorJava extended it, and 
> implemented the FileGenerator interface. I got rid of the 
> Generator2 reference, and also replaced FileGenerador by 
> CodeGenerator, as requested in one issue entry. The 
> workaround was, that GeneratorJava inside created a 
> CodeGenerator instance, but this is no longer needed, since 
> GeneratorJava is a CodeGenerator itself now. As a further 
> consequence, I marked some marked classes/interfaces as 
> deprecated. One should review GeneratorJava now, then it 
> could serve as an example again.
> 
> BTW: I'm still module owner of code generation, but would 
> love to hand it over to someone, because I'm more interested 
> in MDA. But I'm still involved in the import stuff and will 
> take a look on PluggableImport.
> 
> Regards,
> Thomas Neustupny
> 
> Tom Morris wrote:
> > On the code generation side of things, Generator2 has been 
> deprecated 
> > in favor of CodeGenerator, but they don't appear to have equivalent 
> > functionality, so I don't understand how this is meant to work.
> > 
> > Are there examples of modules which have been converted to the new 
> > structure?  Is there a design discussion somewhere which 
> describes how 
> > to convert old style modules to new style modules?
> 

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

Reply via email to