KDevelop4/Manual/Working with templates

From KDE Wiki Sandbox
Revision as of 13:39, 9 July 2012 by Noughmad (talk | contribs) (Created page with "{{ Construction }} Some of KDevelop's code generation features use templates. These define the output structure, while you supply the needed parameters and data. Using templat...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Under Construction
This is a new page, currently under construction!


Some of KDevelop's code generation features use templates. These define the output structure, while you supply the needed parameters and data.

Using templates instead of fixed functionality allows greater flexibility and customizability. Templates can be chosen and modified to suite your particular needs, programming language and coding style. In the cases of project and class templates, they can be shared and downloaded, providing additional functionality to KDevelop without extra code.

Project Templates

Instructions for starting a new project are avaliable in the section Setting up a new project.

File structure

A project template is a compressed archives with specific contents. Every template needs a description file with the same base name as the archive itself, and an extension ".kdevtemplate". Other files are treated as template contents and will be present in the generated project.

my_template.tar.bz2
|
+

Variables

Project templates in KDevelop, just like in KAppTemplate, use KMacroExpander to substitute variable placeholders with their real values. This means that when generating a project, strings of the form %{VARIABLE_NAME} will be replaced with the value of VARIABLE_NAME.

The recognised variables in KDevelop are

  • APPNAME
  • APPNAMELC
  • APPNAMEUC

Class Templates

Documentation Templates