Difference between revisions of "Creating templates"
| Line 16: | Line 16: | ||
<okp = 'http://www.openkm.org/group/property/1.0'> | <okp = 'http://www.openkm.org/group/property/1.0'> | ||
| − | [okg: | + | [okg:tpl] mixin |
| − | - okp: | + | - okp:tpl.name (string) = '' autocreated |
| − | - okp: | + | - okp:tpl.bird_date (string) = '' autocreated |
| − | - okp: | + | - okp:tpl.language (string) = '' autocreated |
</source> | </source> | ||
| Line 28: | Line 28: | ||
"http://www.openkm.com/dtd/property-groups-1.1.dtd"> | "http://www.openkm.com/dtd/property-groups-1.1.dtd"> | ||
<property-groups> | <property-groups> | ||
| − | <property-group label="Sample | + | <property-group label="Sample Template" name="okg:tpl"> |
| − | <input label="Name" name="okp: | + | <input label="Name" name="okp:tpl.name"/> |
| − | <input label="Bird Date" name="okp: | + | <input label="Bird Date" name="okp:tpl.bird_date" type="date" /> |
| − | <select label="Language" name="okp: | + | <select label="Language" name="okp:tpl.language" type="simple"> |
<option label="Java" value="java"/> | <option label="Java" value="java"/> | ||
<option label="Python" value="python"/> | <option label="Python" value="python"/> | ||
Revision as of 12:52, 5 April 2011
As you can see in the User Guide you can create new documents based on templates. But OpenKM offers another feature based in this idea. First of all you need to know the template syntax, which is used by the FreeMarker Template Engine. This engine can be used from making simply variable substitution to loops and other control structure. In this example we use only the basic ones, but you can learn more at FreeMarker Manual.
 |
This section is under construction. |
OpenKM can handle 3 types of template documents:
- PDF
- OpenOffice
- Text (This includes other text-based like HTML, for example)
In order to generate the final document from the template, we need to make an association with a Property Group. The final document also will be assigned the corresponding property group with the user input values, so you can use them for a future search. The three sample template types we will use this Property Groups definition:
PropertyGroups.cnd
<okm = 'http://www.openkm.org/1.0'>
<okg = 'http://www.openkm.org/group/1.0'>
<okp = 'http://www.openkm.org/group/property/1.0'>
[okg:tpl] mixin
- okp:tpl.name (string) = '' autocreated
- okp:tpl.bird_date (string) = '' autocreated
- okp:tpl.language (string) = '' autocreated
PropertyGroups.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE property-groups PUBLIC "-//OpenKM//DTD Property Groups 1.0//EN"
"http://www.openkm.com/dtd/property-groups-1.1.dtd">
<property-groups>
<property-group label="Sample Template" name="okg:tpl">
<input label="Name" name="okp:tpl.name"/>
<input label="Bird Date" name="okp:tpl.bird_date" type="date" />
<select label="Language" name="okp:tpl.language" type="simple">
<option label="Java" value="java"/>
<option label="Python" value="python"/>
<option label="PHP" value="php" />
</select>
</property-group>
</property-groups>
