Community
Participate
Working Groups
Created attachment 258603 [details] example template Gendoc's language would benefit from a unified definition of it's own: - it currently is a mix of acceleo and a tag vocabulary that is gendoc's. This makes the learning curve steeper than necessary. Plus, gendoc language definition depends on Acceleo's roadmap which makes roadmap management potentially complex. Not talking about the fact that, as a template writer, you have to watch at two projects to ensure youre templates still compile. - the gendoc template language would benefit from the AQL query language employed in Sirius for the same reasons as Sirius : simplify the writing of queries, ignoring null values, etc. - last, the fact that gendoc has a language definition of it's own would allow the use of Word's field codes to implement the gendoc vocabulary. This would allows a clean separation between template's parts and the document's parts. This would ease parsing a lot. A last advantage of using Word field codes is that it makes it possible to configure Word's menus to contain the gendoc vocabulary and ease the edition of templates for newcomers and non technical people. The attached docx provides an exemple of what could be such a language. Besides this the tag vocabulary has been added to the Quickpart menu so that template edition benefits from an assistance that is very simple to provide and precious to use.
In order to see the Word fields, the display must be in a mode where field's code are displayed instead of their content. hit Alt-F9 to get in this mode. Alternatively, I provide a screeshot of the template.
Created attachment 258622 [details] screenshot of a template using Word fields.
That is something I have been thinking about, at least to provide the gendoc tags as fields in Word templates. What I don't agree at all is to use Sirius AQL. Rigth now, acceleo and Gendoc use an OMG standard language for the Model-to-text generation: http://www.omg.org/spec/MOFM2T The uses of MOFM2T is an advantage over a proprietary language such as AQL. That it could be a new feature for Gendoc v0.8 / 1.0
