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 "Acceleo/Wishlist"
m (Link to the developer documentation.) |
m (New wishlist elements.) |
||
Line 34: | Line 34: | ||
=== Maven support === | === Maven support === | ||
Acceleo should have a support for maven to manipulate the parser and the engine. | Acceleo should have a support for maven to manipulate the parser and the engine. | ||
+ | |||
+ | === Cheat sheet === | ||
+ | Cheat sheets should be integrated to Acceleo in order to provide the user with tutorials and documentation. | ||
+ | |||
+ | === Code templates === | ||
+ | A preference menu with code templates for Acceleo should be available. | ||
== Parser == | == Parser == | ||
+ | === Distributed parsing === | ||
+ | The Acceleo parser should be able to parse several files at the same time. | ||
== Engine == | == Engine == |
Revision as of 17:42, 4 January 2011
Contents
- 1 The Acceleo Wishlist
- 1.1 How to contribute ?
- 1.2 Tooling
- 1.2.1 Camel case support in the Acceleo tooling
- 1.2.2 Checkstyle for Acceleo
- 1.2.3 Documentation of the standard Acceleo and OCL library
- 1.2.4 Declaration view
- 1.2.5 Call hierarchy
- 1.2.6 Type Hierarchy
- 1.2.7 Smarter highlighting
- 1.2.8 Ant support
- 1.2.9 Maven support
- 1.2.10 Cheat sheet
- 1.2.11 Code templates
- 1.3 Parser
- 1.4 Engine
- 1.5 Other
The Acceleo Wishlist
This page will contain a list of some features that have been requested by members of the Acceleo community and that are not in the roadmap of the Acceleo dev team. Those features may be realized someday and if someone wants to contribute to Acceleo, this is definitely the right place to start. Those features are ranked by type and each of them contains a small summary of the task requested and where to find a possible starting point in the Acceleo source code to realize those features.
How to contribute ?
In order to contribute, you can find here a small guide to create a development environment. After having installed a development environment, you can create a bug entry on the bugzilla here.
Tooling
Camel case support in the Acceleo tooling
We should be able to type something like MAM and Ctrl+Space and have MyAcceleoModule instead for example. It should work for the completion, the quick outline, etc.
Checkstyle for Acceleo
Support for checkstyle rules for Acceleo.
Documentation of the standard Acceleo and OCL library
The completion system should provide the documentation for the Acceleo and OCL operation
Declaration view
The documentation should be available in a documentation view, just like in Java
Call hierarchy
The call hierarchy view and its shortcut (Ctrl+Alt+H) should be available with the same behavior as in the JDT.
Type Hierarchy
The type hierarchy view, its quick view and its shortcut should be available with the same behavior as in the JDT.
Smarter highlighting
The highlighting of a block should not highlight the whole block but its beginning and end. It would be useful for nested "if", "for" and "else".
Ant support
Acceleo should have more Ant tasks to manipulate the parser and the engine.
Maven support
Acceleo should have a support for maven to manipulate the parser and the engine.
Cheat sheet
Cheat sheets should be integrated to Acceleo in order to provide the user with tutorials and documentation.
Code templates
A preference menu with code templates for Acceleo should be available.
Parser
Distributed parsing
The Acceleo parser should be able to parse several files at the same time.
Engine
Compilation on the fly
The AbstractAcceleoGenerator should be changed to allow the compilation on the fly of the mtl files if the emtl files are not found.
Debugging of OCL expressions
The Acceleo debugger should be able to visit the content of an OCL expression.
Other
Export the profiling data into "gprof" file
Acceleo should provide a way to create the data from the profiling as a "gprof" file.