Declaring new meta classes in a TDK code generation transformation patterns model
If you want the generated ACS Code Generator DLL to work with a Modeler item type that is not being worked with at present, you must declare a Meta Class for that Modeler item type.
For more information about Meta Classes, see Declaration of Modeler item types and extended properties - 4G meta classes (TDK).
 |
Do not create new Meta Classes in the same package as the provided Meta Classes - if you do so, your Meta Classes will be lost should you update the TDK Code Generation Transformation Patterns model with improvements provided in a future release of Modeler.
|
To declare a new meta class:
1. Before declaring a new Meta Class for a Modeler item type, check that there is not a Meta Class for that item type in the TDK model already.
The provided Meta Types reside in the Generator::Structure package.
2. Create a new Package in the TDK model that is not scoped to the Generator or TDK Generator Framework packages.
3. In the new Package, create a Class.
4. Set the name of the Class to the Automation Interface name of the Modeler item type. Typically, the automation interface name is the Type name that appears in the Property Pages.
To determine the Automation Interface name of a Modeler item type, see the Automation Interface > Object attributes and associations (item properties and links) section of the Help.
6. If the Meta Class is a child type of another declared Meta Class, create a composite Aggregation link to model the relationship.
|
|
Composite Aggregations between Meta Classes are shown on the Structure class diagram in the Generator::Structure package.
|
After declaring a new Meta Class, declare the extended properties of the Modeler item type with which you want to work. How?