KDevelop5/File template specification
| Under Construction |
|---|
| This is a new page, currently under construction! |
Template language
Class templates use the Grantlee library for rendering templates. It has more features than KMacroExpander, the most important being loops and the ability to expose custom data types from C++ code to templates. The use of Grantlee makes templates more powerful, but also more difficult to write.
For information regarding Grantlee templates in general, refer to its documentation. Since Grantlee's template language is based on Django's, it might be useful to read the Django template documentation as well.
Example template template
There is a project template that creates a new project consisting of a single KDevelop class template. You can use it by starting a new project, choosing and installing this one. Proceeding to create a project using this template will create an example class template.
File structure
Like project templates, class templates are compressed directories, and they too contain a special description file and any number of content files. It is recommended that the description file has a .desktop extension instead of .kdevtemplate, although both are supported.
Unlike with project templates, not all files from the archive are copied to the output directory. Because Grantlee supports template inheritance and inclusions, class templates may contain helper files that only serve for convenience and produce no actual output. The actual output files have to be specified in the template description.
Description file format
Variables
The variables which are passed to class templates are described in the Expression error: Unrecognized word "extragear". API documentation.
Additional templates and filters
Custom options
Templates can expose configuration options to the user prior to the class generation. To do this, add a KConfig XT formatted file into the archive, and specify an Options entry in the template description file pointing to it.
Options=options.kcfg
For information about the options file format, see Using KConfig XT. Note that KDevelop only supports a subset of the KConfig XT specification. Only Int, Bool and String types are recognized, options with other types are ignored. Furthermore, only name, type, label and default attributes are used.