Wish: Transformations

[Thomas_Arnbjerg]

It would be nice if model elements created as part of a transformation are visually marked (like the packages).

Such an indication would allow the developers to identify e.g. classes, which are part of a framework controlled by a transformation and thus avoid unnecessary changes (i.e. changes at their own risk).

I'm trying to do a transformation hierarchy , which separates infrastructure code from the business logic.
In this scenario the design of the infrastructure code should offer a number of well defined hooks, to which the business logic should be attached. The developers should not modify the classes (in the model) associated with the infrastructure (instead the transformation should be adjusted). If I could visually indicate, which model elements are part of which category a lot of explaining and misunderstandings could be avoided.

[Paolo F Cantoni]

Excellent suggestion!

Gets my vote and a "Koala stamp"!

Paolo
PS: don't forget to formally send the suggestion to Sparx (referencing this topic)

[«Midnight»]

I think this would be great!

So, add my vote too.

We might need to come up with a way to differentiate transformations from each other, but that could come later.

Let's see if we can make this work, then we can worry about making it better.

David

[salayande]

Useful feature. Has my support.

Segun

[cuninghamd]

Would be extreamly useful.
 Gets my vote.

Dave.