Closed UrsZeidler closed 10 years ago
We could reuse the tooling logic with the https://wiki.eclipse.org/Acceleo/Getting_Started#Java_services_wrappers
and the localization by using http://stephanebegaudeau.tumblr.com/post/3785590438/improved-properties-files-processing-in-acceleo-3-1 http://www.obeonetwork.com/page/acceleo-properties-files
The only drawback seems is : the templates need to be compiled
Perhaps we need an extension point for registering new templates in the future.
This of course only makes sense when we implementing #27 in which we enable the update capacity.
The gridprint is not bad but it is not based on templates which makes it not so easy providing different layout, also it's a direct printer, we could not provide simpler textbased data reports. As a lot of the model properties are transient as there are calculated, these computation need to be reproduced in a text to text transformation like xslt, so it seems more reasonable to provide the template engine with a "live" object where all these calculated values are present.
Also the template base approach would make it easier for the community providing alternative sheets.
So we are looking for template based model to text engine simply integrating in the rcp.
First we will check out the acceleo engine as it looks like the more mature solution.