Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Acceleo/Wishlist"

m (Other)
m (features)
Line 46: Line 46:
 
=== Improved Acceleo wizard ===
 
=== Improved Acceleo wizard ===
 
The Acceleo wizard allow the user to create an Acceleo project and then to create a UI plugin for Eclipse containing the generators created with Acceleo in order to integrate them seamlessly within Eclipse. This wizard should provide more option for the creation of the µEclipse plugin containing the generator. On of these options could be to be able to have the bundle in the classpath thanks to a classpath container.
 
The Acceleo wizard allow the user to create an Acceleo project and then to create a UI plugin for Eclipse containing the generators created with Acceleo in order to integrate them seamlessly within Eclipse. This wizard should provide more option for the creation of the µEclipse plugin containing the generator. On of these options could be to be able to have the bundle in the classpath thanks to a classpath container.
 +
 +
=== Documentation generation ===
 +
Just like Java can generate a HTML documentation, we would like to be able to generate a HTML version of the Acceleo documentation.
 +
 +
=== Tycho build ===
 +
We should be able to build Acceleo with Tycho.
 +
 +
=== BIRT integration ===
 +
Acceleo should have a connector with BIRT to use the graph framework of BIRT for the profiling or the traceability.
 +
  
 
== Parser ==
 
== Parser ==

Revision as of 03:00, 8 January 2011

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". Should also be implemented to highlight matching parenthesis, brackets, angle brackets... in OCL expressions.

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.

Classpath container

The Acceleo builder/compiler and the Acceleo runtime should be available as classpath container in order to be easily included in Java project within Eclipse. An example of what the result could look like is available here.

Improved Acceleo wizard

The Acceleo wizard allow the user to create an Acceleo project and then to create a UI plugin for Eclipse containing the generators created with Acceleo in order to integrate them seamlessly within Eclipse. This wizard should provide more option for the creation of the µEclipse plugin containing the generator. On of these options could be to be able to have the bundle in the classpath thanks to a classpath container.

Documentation generation

Just like Java can generate a HTML documentation, we would like to be able to generate a HTML version of the Acceleo documentation.

Tycho build

We should be able to build Acceleo with Tycho.

BIRT integration

Acceleo should have a connector with BIRT to use the graph framework of BIRT for the profiling or the traceability.


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.

Stand alone unit testing framework

Acceleo modules should be easy to test thanks to a stand alone testing framework. An example of this framework can be seen here.


Acceleo Portal
Project Project · Installation
Features Acceleo Features · Runtime · Acceleo editor · Views & Perspective · Interpreter · Maven
User documentation Getting Started · User Guide · Acceleo operations reference · OCL operations reference · Text Production Rules · Migration From Acceleo 2.x · Best Practices · Videos · FAQ
Developer documentation Source code · How to contribute · Compatibility · MOFM2T specification · OCL specification
Community Professional Support · Report a bug

Back to the top