FlexDoc.XYZ - Templates / Designer GUI
- Template Components
- Component Properties
- FlexQuery Expression Editors and Assistant Dialog
- Location Path Chooser
- Template Parameters
- Calling Subtemplates
Template components are the building blocks of templates and visualized in FlexDoc Template Designer. Almost everything you can see on the following screenshot depicts some template components.component properties.
Most of the component properties are specified statically in templates using special Property Inspectors:
Some of the component properties, however, can be calculated dynamically depending on the data being processed. Such dynamic properties are specified using FlexQuery-expressions. FlexDoc Template Designer are implemented with the special Expression Editors supplied with the expression quick-check button:
and the button invoking the FlexQuery Expression Assistant Dialog: utility functions, generator variables, template parameters, XML-elements and XML-attributes. This information is always up-to-date since it is obtained not from the static help files but collected dynamically from all available resources. Here is also possible to select the necessary identifier and insert it directly into the edited expression. Location Paths, which are XPath-like expressions used in many settings within templates, can be selected using the special Location Path Chooser dialog:
Each parameter declaration consists of
- parameter name
- data type
- for the
enum-parameter, the list of the possible values
- default value
- other settings
When starting the generator, the template parameters can be either specified in the Template Parameter Inspector dialog:
or passed programmatically, using FlexDoc API. Within the template, the passed parameters can be accessed using FlexQuery-expressions. stock-sections.
Such stock-sections can be called many times from the different template's locations and even from within themselves. subtemplates). Each called subtemplate can produce either the separate document or a fragment of the common document being generated by the calling one. This makes possible
- Using a set of specifically designed templates, to generate any number of logically connected documents, whose creation, names and locations can be controlled by the processed data. In particular, this allows to generate a framed (HTML) documentation.
- To create a library of subtemplates which can be reused many times by calling them from the different application templates. This may help to reduce the project development time as well as to simplify its further maintenance and modifications.
- To generate single (RTF) documents containing section with their own sets of page header/footer.