Editing Bravo (section)

== Features ==

* Static template processing: All templates are read, parsed and processed at compile time, so no extra file access or error handling at runtime is necessary. If the application is supposed to be released in binary form, it's not necessary to ship the template files with the application.

* Multiple templates per file: Some template libraries require the user the create a file for each template, what may be very annoying for a lot of small templates. Bravo allows the user to define multiple templates per file with arbitrary comments between them. This means template documentation can be embedded directly into the template files.

* Conditional template evaluation: Bravo provides conditional template splices (see below), allowing to check conditions at runtime. This removes misplaced logic from the program source code and leads to a cleaner separation of program logic and layout. Beyond that, it helps to decrease the number of templates.

* Embedding of Haskell expressions: Bravo allows the user to embed arbitrary Haskell expressions combined with template variables.

* Customized data type generation: For the data type creation by default the following naming scheme is used:
** For a given template name <code>"name"</code>, the created data type/constructor name is <code>"TplName"</code>.
** For a template <code>"name"</code> and a template variable <code>"var"</code> a record field <code>"nameVar"</code> is created.
:This behaviour can be changed by the <code>mkTemplatesWithOptions</code> and <code>mkTemplatesFromFileWithOptions</code> functions, that allow you to customize this naming scheme.