I did read the Andromda vision document these days and I can't remember if this was a concern on that. I believe that performance (speed and memmory) must aways be a concern on the project, since for the user doing all the generation for all the files again and again for really very big production models may be impracticable.
As a user, I think if, because MDR does not supply the means, is not easily feasible to detect modifications automaticaly, in the short term it should be left some means to the user chose what to process or not on the generation step. This seems to be the approach adopted by Metanology's MDE.
[]'s
Charles
| "Matthias Bohlen" <[EMAIL PROTECTED]>
27/11/2003 15:56
|
To: <[EMAIL PROTECTED]> cc: "'Users AndroMDA'" <[EMAIL PROTECTED]> Subject: RE: [Andromda-user] Re-generation of unmodified model classes |
Hi Charles,
there is no possibility for AndroMDA to detect whether a single model element has changed (Netbeans MDR does not supply this info). It can only detect whether the whole model has changed. But this is not what you want, right?
Sorry...
Matthias
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, November 27, 2003 7:37 PM
To: [EMAIL PROTECTED]
Subject: [Andromda-user] Re-generation of unmodified model classes
Is there any intelligent way for Andromda to NOT re-generate files for unmodified classes in the model? If not, Is this at last a ongoing work in version 3.x?
I'm playing with Andromda 2.x and I'm very happy with him, but that is a limiting problem on doing it for production as model grows over.
[]'s
