Difference between revisions of "ATL Wish List"

From Eclipsepedia

Jump to: navigation, search
Line 1: Line 1:
* Hierarchical packages
+
* Allow hierarchical packaging (extends a!b to a!b.c…)
* Module level inheritance
+
* Allow module level inheritance  
* Bound the metamodel to the model name
+
* Provide short names as well as long names for metamodels
* User Interface improvement
+
* Bind the metamodels to their name(s) (AM3)
* Bidirectional transformations (e.g. a solution based on AMW or a solution based on Constraint Logic Programming)
+
* Improve the User Interface (AM3)
* Debug mode on console: stop or continue an ATL transformation after an error
+
* Possible generation of bidirectional transformations:
* Warm about "nullable" access (for example in OCL Query
+
    - A solution based on AMW has been presented by Frédéric Jouault
* Type checkers/static Analyzer
+
    - A solution based on Constraint Logic Programming has been proposed by Marc Pantel
* Syntaxtic enhancement for resolveTemp
+
* Improve  the  debug  mode and  console (offer  the  possibility  to  stop or continue an ATL transformation after errors, …)
* Porting of the virtual machine on embedded systems
+
* Warm about unchecked “nullable” accesses (for example in OCL queries)
* New model handlers
+
* Provide static analyzers (for example a type checker…)
* New injectors
+
* Syntactic enhancement for the “resolveTemp” function (new name, …)
* Wiki web site for frequently asked questions. It is possible to use the wiki provided by Eclipse
+
* Possible porting of the ATL virtual machine on embedded systems : provide “smaller” version of the ATL VM
* Support for using different files for defining a metamodel (What is a metamodel extension?)
+
* Implement new model handlers  
* Editor for ATL extensions
+
* Implement new injectors  
* Pluggable Navigation Languages
+
* Create a wiki web site for frequently asked questions (FAQ). It seems to be possible to use the wiki provided by Eclipse…
 +
* Provide an extended way to define metamodels:
 +
    - Provide support for using different files for defining a metamodel (technical solution)
 +
    - Define metamodel’s extensions (conceptual solution)  
 +
* Provide editor(s) to allow ATL extensions  
 +
* Pluggable navigation languages (OCL of course but also other ones like XPath, XQuery, …)

Revision as of 12:40, 11 May 2006

  • Allow hierarchical packaging (extends a!b to a!b.c…)
  • Allow module level inheritance
  • Provide short names as well as long names for metamodels
  • Bind the metamodels to their name(s) (AM3)
  • Improve the User Interface (AM3)
  • Possible generation of bidirectional transformations:
   - A solution based on AMW has been presented by Frédéric Jouault
   - 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, …)
  • Warm about unchecked “nullable” accesses (for example in OCL queries)
  • Provide static analyzers (for example a type checker…)
  • Syntactic enhancement for the “resolveTemp” function (new name, …)
  • Possible porting of the ATL virtual machine on embedded systems : provide “smaller” version of the ATL VM
  • Implement new model handlers
  • Implement new injectors
  • Create a wiki web site for frequently asked questions (FAQ). It seems to be possible to use the wiki provided by Eclipse…
  • Provide an extended way to define metamodels:
   - Provide support for using different files for defining a metamodel (technical solution) 
   - Define metamodel’s extensions (conceptual solution) 
  • Provide editor(s) to allow ATL extensions
  • Pluggable navigation languages (OCL of course but also other ones like XPath, XQuery, …)