Grantlee  5.1.0
Using Grantlee in your application

Using Grantlee in Qt applications will often not require much code.

Grantlee::Engine *engine = getEngine();
Template t = engine->loadByName( "mytemplate.html" );
Context c;
c.insert( "some_input", some_value );
browser.setHtml( t->render( c ) );

Error handling etc is omitted for clarity. In order for the above to work as expected, it is necessary to configure the build system to find Grantlee, and to configure Grantlee to find templates and plugins.

Finding Grantlee with CMake

Grantlee uses the CMake cross platform build system, and installs a cmake file called Grantlee5Config.cmake. This config file is automatically searched for by CMake and contains the information needed for other CMake based applications to find headers and link against Grantlee libraries.

When creating an application using CMake that depends on Grantlee, first issue the find_package command, and then use the CMake target_link_libraries command link to and use the libraries.

project(my_application)
cmake_minimum_required(VERSION 2.8.11)
set(CMAKE_AUTOMOC ON)
set(CMAKE_INCLUDE_CURRENT_DIR ON)
find_package(Grantlee5 REQUIRED)
# ... Application sources etc.
target_link_libraries(
my_application
Qt5::Widgets
Grantlee5::Templates
)

Deploying Templates

Template files can be installed by your application and must later be found by Grantlee so they can be used. If the files are installed on the filesystem, the path they were installed to can be specified when creating a TemplateLoader.

Engine* getEngine()
{
Engine *engine = new Engine( this );
loader->setTemplateDirs( QStringList() << path_to_installed_templates );
engine->addTemplateLoader( loader );
return engine;
}

It is also possible to compile the templates into a Qt Resource file and set the resource URL on the TemplateLoader.

# my_app_templates.qrc:
<!DOCTYPE RCC><RCC version="1.0">
<qresource>
<file>mybasetemplate.html</file>
<file>mytemplate.html</file>
<file>myothertemplate.html</file>
</qresource>
</RCC>
# CMake code:
set (_rcc_file "my_app_templates.qrc")
qt5_add_resources(_template_rcc_src ${_rcc_file} OPTIONS -root "/templates/" )
add_executable(my_app, ${my_app_srcs} ${_template_rcc_src})
# Application code:
loader->setTemplateDirs( QStringList() << ":/templates/" );
engine->addTemplateLoader( loader );

The -root option passed to rcc in CMake causes the templates to be in the virtual filesystem location ":/grantlee/mytemplate.html" etc. This name spacing helps keep independent data in the virtual filesystem separate.

Finding user defined templates

If users are able to define their own templates in an application that uses Grantlee for theming for example, the path to the location of such potential templates must also be set through the TemplateLoader. Paths to user defined templates should be defined before default/installed templates so that the user templates are found first. If there is a reason to disallow user overriding of certain templates, they can be specified in a separate TemplateLoader.

no_override_loader->setTemplateDirs( QStringList() << path_to_non_overridable_templates );
engine->addTemplateLoader( no_override_loader );
override_loader->setTemplateDirs( QStringList() << path_to_user_templates << path_to_default_templates );
engine->addTemplateLoader( override_loader );

Additionally, the External binary resources feature could be used to allow savvy users to share themes/templates in a package, or to deploy updated templates easily to existing deployed applications.

Finding tags and filters

Grantlee looks for plugins in the paths from the Engines pluginPath property. It does so in the same order they appear there.

The property defaults to the following directories

Each path has "grantlee/$version/" appended to it, and the resulting directory is searched for plugins. For example, if the version of Grantlee is 0.2 and QCoreApplication::libraryPaths() contains "/usr/lib/plugins/", the directory "/usr/lib/plugins/grantlee/0.2" would be searched for plugins. The search stops when a plugin matching a particular name is found.

The paths used to search for plugins can be overriden by using Engine::setPluginPaths. If you just want to add some additional paths use Engine::addPluginPath. The added path will be prepended to the list of search paths.

Deploying custom tags and filters

Custom tags and filters can be defined in C++ code or in QtScript.

To create a custom C++ plugin it must be built as part of a library and installed in a location known to the application.

# CMake code
include(${Grantlee_USE_FILE}) # This files defines the grantlee_add_plugin macro
grantlee_add_plugin(my_custom_plugin
custom_plugin_library
TAGS
custom_tag1
custom_tag2
custom_tag3
FILTERS
custom_filter1
custom_filter2
custom_filter3
)
install(TARGETS my_custom_plugin
RUNTIME DESTINATION ${PLUGIN_INSTALL_DIR}
LIBRARY DESTINATION ${PLUGIN_INSTALL_DIR}
ARCHIVE DESTINATION ${LIB_INSTALL_DIR}
COMPONENT Devel
)

In this case, my_custom_plugin is a name used for the plugin in the CMake environment. It is used to install the custom library in the install command.

custom_plugin_library.cpp is the C++ file where you implement the Grantlee::TagLibaryInterface to return custom tags and filters. The custom tags and filters files are given with the TAGS and FILTERS arguments to the macro. Note that moc is not run on the headers of files given in the FILTERS argument, and is run on the headers of files given in the TAGS argument (custom_tag1.h etc) and on the main library file, in this case custom_plugin_library.h.

Note that the PLUGIN_INSTALL_DIR given to the install command should contain the version number of Grantlee used to create the custom library. For example, /usr/share/my_app/plugins/grantlee/0.1/.

In C++ code, it is necessary to either instruct the Grantlee::Engine about the location of the plugins or to configure your QCoreApplication::libraryPaths by another standard method. Note that it is possible to define custom versions of built in tags and filters by putting your own plugin library in the path before the path to the default Grantlee plugins.

For example, if your custom plugin library contained a custom implementation of the {% for %} tag:

Engine *engine = new Engine( this );
engine->setPluginPaths( QStringList() << path_to_custom_plugins << path_to_grantlee_defaults );

Note that neither the path to the custom libarary nor the path to the Grantlee default library should contain the version number when specified in C++ code with the Engine. The version is only specified when installing the plugin in CMake.

Custom tags and filters implemented in QtScript can also be deployed on the file system, or, like template files, can also be deployed in Qt Resource files. In that case, the version should be specified in the -root argument in CMake.

# CMake code:
set (_rcc_file "my_qtscript_library.qrc")
qt5_add_resources(_scripted_rcc_src ${_rcc_file} OPTIONS -root "/plugins/grantlee/${Grantlee5_VERSION_MAJOR}.${Grantlee5_VERSION_MINOR}" )
add_executable(my_app, ${my_app_srcs} ${_scripted_rcc_src})
# C++ code:
engine->setPluginPaths( QStringList() << ":/plugins/" );

Note again that when specifying the path in the virtual filesystem, the version is omitted. User defined filter written in QtScript can also be located similiarly to templates from either the filesystem or the Qt Resource virtual filesystem.

Building Grantlee

It is possible to build only parts of Grantlee if your application is a QCoreApplication that depends only on QtCore

dot_moduledeps.png
Dependency Graph for Grantlee
dot_plugindeps.png
Dependency Graph for Grantlee plugins

The appropriate options may be specified in the cmake gui, or on the command line.

mkdir build && cd build
cmake .. -DBUILD_GUI:BOOL=OFF -DBUILD_TESTS:BOOL=OFF -DBUILD_SCRIPT_PLUGIN:BOOL=OFF

Similarly, it is possible to build only grantlee_gui standalone

mkdir build && cd build
cmake .. -DBUILD_CORE:BOOL=OFF -DBUILD_TESTS:BOOL=OFF -DBUILD_MAIN_PLUGINS:BOOL=OFF -DBUILD_SCRIPT_PLUGIN:BOOL=OFF