ATLflow help
Release Notes
-
Release Notes
-
ATLFlow 0.0.24
-
ecore model
-
ant task
-
ATLFlow 0.0.23
-
ui
-
generators
-
ATLFlow 0.0.22
-
bugfixes
-
ATLFlow 0.0.21
-
generators
-
ATLFlow 0.0.20
-
ecore model
-
gmf transformation
-
ui
-
ATLFlow 0.0.19
-
ecore model
-
gmf transformation
ATLFlow 0.0.24
ecore model
The calls object has a name, also there is a default predicate in the callable to
evaluate. An other changes on the callable is a new flag to synconize the workspace after execution. Switch, Property, and Generator are now Documentable. The missing basic predicate true/false are defined by a
boolean predicate. A
stop element is added to be able to define the end of a transformation flow in a switch.
ant task
There is an ant task to execute defined workflows. See
ant task.
All changes in the release
0.0.24.
ATLFlow 0.0.23
ui
There is a new eef generated editor available.
Some new transformation templates :
- eef template
- acceleo textile report
generators
Some new generators :
All changes in the release
0.0.23.
ATLFlow 0.0.22
bugfixes
The externalCallable diagram element was removed from the diagram by a semantic update.
The eef generator calls EcoreUtil.resolveAll to resolve the proxies when the genmodel is loaded.
All changes in the release
0.0.22.
ATLFlow 0.0.21
The eef propertie view tabbed is added to the properties view, the view allows you to edit the predicate in PredicateSwitch and CompositePredidactes directly.
generators
Added preferences for some generators to define the meta model uris they work on and one new generator frameworks are added.
- eef properties initializer and code generator
- Acceleo code generator
All changes in the release
0.0.21.
ATLFlow 0.0.20
A new template project wizard is added,it contains parameterized transformation chains like generating a gmf editor, which is equals to the „../samples/generateGMF.html” other wizard. A short cut in the context menu let you create an appropriated start config and definition file.Now the transformation can be controlled by the PropertyValueSwitch and the PredicateSwitch element. You can also call other callable elements in different processes with the ExternalCall element.
ecore model
- A
Predicate and
PropertyValueSwitch PropertyValueSwitch are introduced as flow control elements.
- The
externalCall element is a kind of subprocess, calling a delegates Callable and returns to the next Callable.
Changes in the gmf process.
- You can add labels without a feature to a node or link. In the custom.atl file is a map to define them and set default values.
- There is a new FigureRule to create simple Label figures called ‚label’.
- Variable _plugin_name_ and _fileextension_name_ let you define the equally properties for the transformation.
ui
Changes in the ui.
- A ‚new wizard’ has been added, it creates a project with template transformation flows.
- For the ecore model file a .popup menu is available to create a lauchconfiguration and custom.atl file usable with the template transformation for GMF.
All changes in the release
0.0.20.
ATLFlow 0.0.19
The model contains a property element for substitution in artifact URI and name.
- These properties have a default value. In the start configuration it is be possible to set a property value.
- To define the properties and set the values there is a tabbed property section to define them, just like the EAnotaions in the ecoretools editor.
- The substitution of properties affect the artifact URI, the property name it self, and the artifact name.
- A property can be defined by another property, eg. ${base} = XXX ${baseExtension}=${base}YYY will produce XXXYYY for ${baseExtension}
- There are several dialog types,„string” for a simple input dialog, „resource” for a workspace resource, „container” for a workspace container, and „uri” for a ExtendedLoadResourceDialog. These dialog will popup if selected in the launch configuration.
ecore model
The ecore model has changed.
- The generator instances are removed from the ecore model.
- A property element was added.
- The namespace has to change to http://urszeidler.de/callchain/2010/flowmodel.
- There is a called rule for choosing the figure role (createFigure ), there are at the moment only two called rules „svgFigure” and „default”.
- For svgFigure there is map in the configuration file „svgUris” where the uris can be mapped for a element.