Book a Demo

Author Topic: code generation smartness  (Read 2281 times)

mschipperheyn

  • EA User
  • **
  • Posts: 21
  • Karma: +0/-0
    • View Profile
code generation smartness
« on: December 30, 2005, 03:26:31 am »
When I have an existing project which has already generated code, I can update the code. When I add new classes and child packages to a particular package structure, I want to update my generated code without wiping existing materials. This doesn't work very well.

If you select auto generate code, it basically overwrites everything even if you select synchronize model and code

If you select do not generate, it will not overwrite your files, however, it will handle newly to be generated files poorly. What you expect is for EA to "know" where the files live, because it has already generated the existing files in a particular place and knows about the package structure. Instead you have to manually place each file in its new place. You get a dialogue for each file. It also doesn't generate newly created subpackages.

Any way to get past his akwardness?

Kind regards,

Marc

mschipperheyn

  • EA User
  • **
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Re: code generation smartness
« Reply #1 on: December 30, 2005, 03:46:32 am »
another bug:
When you choose synchronize package contents, you get these little popups warning you that something in the code is not available in model. When you choose delete, in stead of deleting the attribute or method, EA does nothing...

Marc