Architecture of Text Templates

The text template transformation process takes a text template file as the input, performs the transformation on the input, and generates a text file as the output. The text template transformation process has three components: the engine, the host, and one or more directive processors. This section contains topics that discuss the architecture of the text template transformation process in detail.

In This Section

• Architecture of the Text Template Transformation Process
  Explains the architecture of the text template transformation process, including the host, engine, and directive processor components.

• Accessing Models from Text Templates
  Explains how to call a generated directive processor so that you can access a model from a text template.

• How to: Call a Generated Directive
  Lists the steps to call a generated directive processor so that you can access a model from a text template.

• How to: Call a Custom Directive
  Lists the steps to call a custom directive processor so that you can access custom functionality from a text template.

Reference

Domain-Specific Language Tools

Related Sections

• Using Built-in Directives in Text Templates
  Contains topics that explain using built-in directives, such as output and include, in text templates.

• Adding Code to Text Templates
  Contains topics that explain adding code, such as statements and expressions, to text templates.

• Advanced Tasks with Text Templates
  Contains topics about advanced text template tasks, such as creating custom host and directive processor components.

• Domain-Specific Language Tools Glossary
  Defines key terms that are used in the Help for Domain-Specific Language Tools.

• Working with Domain-Specific Language Solutions
  Describes the solution templates that you can use to create different types of domain-specific language solutions by using Domain-Specific Language Tools.