Refactoring Function

[malmoth]

I'd like that EA provides the ability to rename a class or interface (or whatever) throughout the whole project including the generated source files.
Indeed, if one rename a class with EA HMI, this will only change the class declaration, and every other call of the class will refer to the former name, and the project won't compile.

[«Midnight»]

I agree. This could apply throughout the model: attributes, states, whatever.

Of course some of this works now, but for classes and interfaces it can be a bit dicey at best.

There are also issues if you are round tripping code generation. Severl of the forum gurus have suggested (my word) that forward generation is where we should be putting our emphasis, so the ability to globally reflect name changes would fit right in - make the change and build a new output tree.

[jeshaw2]

This might be a nice feature, but if implemented, I'd like the propagation to be optional or optionally constrained to the current package or view.

[«Midnight»]

Good point Jim,

Considering all the things we use packages for, and the reasons behind them, there should be some way to limit the 'global' implications of such a change. Beats going back to the good old days before namespaces.

Something along the lines of VS' scoping for search and replace - you can limit to the current procedure, file, or everything.

[jeshaw2]

Exactly!

In addition to using EA in my consulting practice (where the diagrams are various views on the same project), I often use an EA project either for my lectures or as a repository for figures in several (disjoint) monographs.  

In an EA project supporting my monographs and lectures, the individual diagrams do not necessarily relate to the same physical project.  Making changes in one diagram should not have side effects in another.

I need control of the domain of the change.