Skip to main content
Jump to: navigation, search

Difference between revisions of "Henshin/Graphical Editor"

(Initial contribution)
 
m
Line 5: Line 5:
 
The rule is called ''Test'' and it matches two object, one of type ''Library'' and one of type ''Writer''. Additionally, the writer instance must be contained in the library instance via the ''writers'' containment reference, and its ''name'' attribute must be set to "Smith". The last condition that must be fulfilled for that rule to be applicable is that the library instance must not contain a instance of type ''Book'' in its ''books'' containment reference.
 
The rule is called ''Test'' and it matches two object, one of type ''Library'' and one of type ''Writer''. Additionally, the writer instance must be contained in the library instance via the ''writers'' containment reference, and its ''name'' attribute must be set to "Smith". The last condition that must be fulfilled for that rule to be applicable is that the library instance must not contain a instance of type ''Book'' in its ''books'' containment reference.
  
If these conditions are all fulfilled, the rule can be applied. It performs the following actions in an atomic step: delete the writer instance from the library and create and add a book instance to the library.
+
If these conditions are all fulfilled, the rule can be applied. It performs the following actions in an atomic step: delete the writer instance from the library and create and add a book instance to the library. Note that you can also define attribute calculations (not shown in this example).
 +
 
 +
If you look at the tree-based editor, you see that the graphical notation is quite different from the underlying model. The Henshin transformation model allows you to define very complex in-place transformations. The graphical editor currently does not support all of the powerful language concepts, yet.

Revision as of 17:00, 5 March 2010

Model transformations in Henshin are defined using matched transformation rules. There are currently two rules editors available: a tree-based editor (EMF) and a graphical one (GMF). A screenshot of a simple, but not very meaningful, transformation rule in both editors is shown below.

Henshin example transformation rule.png

The rule is called Test and it matches two object, one of type Library and one of type Writer. Additionally, the writer instance must be contained in the library instance via the writers containment reference, and its name attribute must be set to "Smith". The last condition that must be fulfilled for that rule to be applicable is that the library instance must not contain a instance of type Book in its books containment reference.

If these conditions are all fulfilled, the rule can be applied. It performs the following actions in an atomic step: delete the writer instance from the library and create and add a book instance to the library. Note that you can also define attribute calculations (not shown in this example).

If you look at the tree-based editor, you see that the graphical notation is quite different from the underlying model. The Henshin transformation model allows you to define very complex in-place transformations. The graphical editor currently does not support all of the powerful language concepts, yet.

Back to the top