Skip to main content
Jump to: navigation, search

ATL Wish List

Unimplemented Features

Language Enhancements

  • Allow module level inheritance
  • Provide short names as well as long names for metamodels
  • Syntactic enhancement for the “resolveTemp” function (new name, …)
  • Provide an extended way to define metamodels:
    • Define metamodel’s extensions (conceptual solution)
  • Pluggable navigation languages (OCL of course but also other ones like XPath, XQuery, …)

Implementation Enhancements

  • Bind the metamodels to their name(s) (AM3)
  • Improve the User Interface (AM3)
  • Possible generation of bidirectional transformations:
    • A solution based on AMW is given in the UMLProfiles example
    • A solution based on Constraint Logic Programming has been proposed by Marc Pantel
  • Improve the debug mode and console (offer the possibility to stop or continue an ATL transformation after errors, …)
  • Provide static analyzers
    • a type checker…
    • a checker for “nullable” accesses (for example in OCL queries)
  • Possible porting of the ATL virtual machine on embedded systems : provide “smaller” version of the ATL VM
  • Implement new model handlers
    • Improve support for the UML2 Eclipse plugin (remark: see why this is required at ATL Model Handlers)
    • Improve support for the RSA Eclipse plugin (same remark)
  • Implement new injectors and extractors
  • Provide editor(s) to allow ATL extensions

Features Currently Being Tested

  • Allow hierarchical packaging (extends a!b to a!b.c…)

Latest CVS version enables the use of <metamodel-name>!<package-name>::<class-name> for EMF. This patch provides the same feature for MDR.

  • Provide support for using different files for defining a metamodel (technical solution)

This feature is implemented by this patch.

  • Create a wiki web site for frequently asked questions (FAQ). It seems to be possible to use this wiki provided by Eclipse…

Back to the top