Metamodel Integration After the generator language itself, the main language
visible in a generator is the modeling language. The generator editor should therefore
alloweasy navigation and selection of the concepts of the modeling language and their
properties. In simple cases it is possible to update generators automatically when the
names of modeling language concepts change.
The generators themselves will normally be associated with a speci?¬?c modeling
language: they can only sensibly be run on models of that type, and will contain
references to the concepts of that modeling language. It would be possible to go
further, and allow generators to be associated with individual object, relationship and
even property types. In our experience, however, a full generator will normally consist
of less than a few dozen subgenerators. As this is approximately equal to the number
of concepts in the corresponding modeling language, scattering the parts of the
generator across all types will make generator development less manageable.
Tracing from Output to Models and Generators Particularly while building
generators, it is useful to be able to track a given piece of output back to the model
element and generator command that produced it. In cases where the intention is not to
hide generated code from modelers, being able to track back from output to model is
even more useful.
Pages:
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733