my main problem is to document the template tags (the object i am binding to the template). what i imagine in the word add in is:
- see all properties of my data source, clicking on the property would create the appropriate aspose tag
- if there is a list of object, clicking on the list would create a foreach tag. additional feature for list can be imagined : define sort, filter option (that would generate the appropriate linq where code in the template)
- if i am in a paragraph somewhere in my document template, the word addin would propose me the current object with all properties that i can insert. When building a template it is difficult, especially for a non developer to know which property can be accessible to insert the appropriate tag. in our datasource, we have different level of list : an object contains a list of ClassA which contains a list of ClassB. so in the template we have a foreach in a foreach. in the first foreach, only classA properties are accessible. If you have a complex datasource with a lot of properties, the template creation is time consuming.
- in the word addin, have the possibility to add a template sample (directly a preformated template, for example a table containing a list of customers)
the word add in api proposes all functions to manipulate the current word document. the word addin i imagine is simply a tool to create an aspose linq report with the right aspose tag. When the template is created, it can be used in our application to generate the report (just like now).
The word addin does not require modification in the aspose.words .net api, this is a tool to help us create an apsose linq report template.
what do you think ?