Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "ATL 3.1.0 New and Noteworthy"
| Line 1: | Line 1: | ||
==Helios Release== | ==Helios Release== | ||
| − | |||
| − | |||
| − | |||
The ATL Toolkit is now compatible with Eclipse Helios (Eclipse 3.6, EMF 2.6). | The ATL Toolkit is now compatible with Eclipse Helios (Eclipse 3.6, EMF 2.6). | ||
| + | TODO | ||
==ATL Editor improvements== | ==ATL Editor improvements== | ||
| − | * | + | *Hover informations |
| − | * | + | TODO |
| − | + | [[Image:atl_hover.png]] | |
| − | * | + | |
| − | * | + | *Open declaration (both available with F3 and Ctrl-click) |
| + | TODO | ||
| + | [[Image:atl_open_declaration.png]] | ||
| + | |||
| + | *Content assist | ||
| + | TODO | ||
| + | [[Image:atl_advanced_content_assist2.png]] | ||
| + | |||
| + | *Occurences highlighting | ||
| + | TODO | ||
==ATL Language== | ==ATL Language== | ||
| − | + | ===''pcall''=== | |
| − | + | TODO | |
| + | |||
| + | ===Output Model selection=== | ||
| + | |||
| + | A miss in the ATL syntax has just been corrected: the '''in''' keyword is now available for both input and output patterns. It mainly allow to specify in which model you want to create elements, when the old semantics forbade the use of several output models conforming to the same metamodel declaration. The workaround wasn't very intuitive as it consists on declaring the same metamodel with different names... | ||
| + | |||
| + | The use of this keyword is described at the end of [[ATL/User_Guide_-_The_ATL_Language#Simple_target_pattern_element|this]] section. | ||
==Debugging & Profiling== | ==Debugging & Profiling== | ||
| − | + | ===debugger refactoring=== | |
| − | + | TODO | |
| + | |||
| + | ===profiler=== | ||
| + | TODO | ||
==ATL Plugins== | ==ATL Plugins== | ||
| − | + | The ATL plugin wizard is a new feature which helps achieving an ATL programmatic launch. This utility first will ask for transformation parameters (metamodels, libraries paths, transformation modules paths): | |
| − | *standalone use | + | |
| + | [[Image:atl_plugin_wizard.png]] | ||
| + | |||
| + | Then a new plug-in will be generated, embedding: | ||
| + | *the transformation modules and libraries | ||
| + | *a propery file containing URIs, atl file paths | ||
| + | *a Java class which allow to programmatically launch the ATL transformation | ||
| + | |||
| + | [[Image:atl_plugin_wizard_result.png]] | ||
| + | |||
| + | Finally you will be able to launch the transformation using the generated main, or integrating the launcher class into an existing application. To use the transformation as a standalone app, you can use Eclipse PDE export options: | ||
| + | |||
| + | [[Image:atl_plugin_wizard_result_export.png]] | ||
| + | |||
| + | This will product a .jar containing all the required ATL, Eclipse and EMF libraries. | ||
Revision as of 08:54, 9 June 2010
Contents
Helios Release
The ATL Toolkit is now compatible with Eclipse Helios (Eclipse 3.6, EMF 2.6). TODO
ATL Editor improvements
- Hover informations
TODO File:Atl hover.png
- Open declaration (both available with F3 and Ctrl-click)
TODO File:Atl open declaration.png
- Content assist
TODO File:Atl advanced content assist2.png
- Occurences highlighting
TODO
ATL Language
pcall
TODO
Output Model selection
A miss in the ATL syntax has just been corrected: the in keyword is now available for both input and output patterns. It mainly allow to specify in which model you want to create elements, when the old semantics forbade the use of several output models conforming to the same metamodel declaration. The workaround wasn't very intuitive as it consists on declaring the same metamodel with different names...
The use of this keyword is described at the end of this section.
Debugging & Profiling
debugger refactoring
TODO
profiler
TODO
ATL Plugins
The ATL plugin wizard is a new feature which helps achieving an ATL programmatic launch. This utility first will ask for transformation parameters (metamodels, libraries paths, transformation modules paths):
Then a new plug-in will be generated, embedding:
- the transformation modules and libraries
- a propery file containing URIs, atl file paths
- a Java class which allow to programmatically launch the ATL transformation
File:Atl plugin wizard result.png
Finally you will be able to launch the transformation using the generated main, or integrating the launcher class into an existing application. To use the transformation as a standalone app, you can use Eclipse PDE export options:
File:Atl plugin wizard result export.png
This will product a .jar containing all the required ATL, Eclipse and EMF libraries.