If you are using the TemplateJinn framework then
you will undoubtedly need to declare at least one compiler and one embed
compiler. More than likely you will at least declare the prepackaged
Jinn tag compiler and Jinn embed compiler.
Declaring compilers is just like declaring multiple modules in one big array.
For information about declaring modules see the Modules
Documentation. The only exception is that at least one of the components
of the module must have a name of
compiler. The following example illustrates the
declaration process:
$GLOBALS['interJinn']['compilers'] = array
(
array
(
'logic' => array
(
array
(
'name' => 'compiler',
'source' => '///Core/compilers/jinnTag.inc',
),
),
),
array
(
'logic' => array
(
array
(
'name' => 'compiler',
'source' => '///Core/compilers/compactLines.inc',
),
),
),
);
Declaring embeds is just like declaring compilers. The reason for declaring embeds separately is because the above compilers and embed compilers are managed differently. The embed manager allows the value of an embed to be retrieved at any point/ This means that a tag compiler or any other compiler you create can request the resolution of an embed value before the actual embed compiler is run on the remaining content.
$GLOBALS['interJinn']['embeds'] = array
(
array
(
'logic' => array
(
array
(
'name' => 'compiler',
'source' => '///Core/compilers/jinnEmbed.inc',
),
),
),
);