<?xml version="1.0"?>
<!-- Generated by the OpenACS Package Manager -->

<package key="acs-templating" url="http://openacs.org/repository/apm/packages/acs-templating/" type="apm_service">
    <package-name>Templating</package-name>
    <pretty-plural>Templating Services</pretty-plural>
    <initial-install-p>t</initial-install-p>
    <singleton-p>t</singleton-p>
    
    <version name="5.3.2" url="http://openacs.org/repository/download/apm/acs-templating-5.3.2.apm">
        <owner url="http://openacs.org">OpenACS</owner>
        <summary>Templating library.</summary>
        <release-date>2007-07-18</release-date>
        <vendor url="http://openacs.org">OpenACS</vendor>
        <description format="text/html">The templating system provides the tag library and support routines
that allow developers and graphic designers to work
independently. Templates specify the layout of the page seperately
from the contents of the page. Graphic designers work primarily on the
layout part of the template (the template), while programmers work
primarily a script that generates the the content part of the template
(the code). In addition, the template system provides a way to use a
single layout specification for many physical pages, so the overall
layout of a site can be more easily administered.
</description>
        <license>GPL version 2</license>
        <maturity>3</maturity>

        <provides url="acs-templating" version="5.3.2"/>
        <requires url="acs-kernel" version="5.3.2"/>

        <callbacks>
            <callback type="before-upgrade"  proc="template::apm::before_upgrade"/>
        </callbacks>
        <parameters>
            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="DefaultFormStyle"  default="standard" description="The default form template to use if a particular form does not explicitly specify the form style to use."/>
            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="DefaultListFilterStyle"  default="filters" description="The default list filter template to use if a particular listfilter tag does not explicitly specify the list filter style to use."/>
            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="DefaultListStyle"  default="table" description="The default list template to use if a particular list does not explicitly specify the list style to use."/>
            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="RefreshCache"  default="as needed" description="When to re-translate templates.  Values: never, as needed, always."/>
            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="RichTextEditor"  default="rte" description="Use the specified javascript text editor when UseHtmlAreaForRichtextP is activated. Valid arguments are &quot;rte&quot; or &quot;xinha&quot;."/>
            <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="ShowCompiledTemplatesP"  default="0" description="Show thecompiled template (for debugging) at .cmp URL"/>
            <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="ShowDataDictionariesP"  default="0" description="Offer data dictionaries on .dat/.fmt URL."/>
            <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="SpellcheckDialectsP"  default="0" description="Do you care about dialects or not? If this is set to '1' all available dictionary dialects for all available languages will appear as choices in the pull-down menu. If the param is set to '0', only the base-language(s) will be shown. However, it only works with aspell - on ispell you'll simply get a 'yes' and 'no' option, no matter how this param is set, where 'yes' will use ispell's default dictionary. NOTE! You'll need to restart the server for this param to take effect."/>
            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="SpellcheckFormWidgets"  default="textarea 0 richtext 0" description="The widgets that you specify here will be spellcheck enabled in all forms (that use ad_form / form builder). Adding a 'nospell' flag to a form element overrides this parameter and disables spellchecking of that element. The format of this parameter is such: 'widget 1 widget 0 ...', where 'widget' stands for one of the form widgets that are possible to spellcheck enable: text, textarea, richtext. '1' after 'widget' indicates that the default should be to spellcheck; '0' means the user has to manually state that spellchecking should be performed on the form element. In order to enable spellchecking via this parameter either the aspell or ispell binary (or both, in which case aspell takes precedence) must be installed on the server. The path to the binary is auto-detected on server startup. If the parameter is left blank, spellchecking will be disabled altogether."/>
            <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="UseHtmlAreaForRichtextP"  default="1" description="Should the richtext widget use the htmlArea widget for richtext editing. 1 = yes, 0 = no. We will also check the browser's User-Agent header to find out if htmlArea works with the given browser."/>
            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="XinhaDefaultPlugins"  default="GetHtml CharacterMap ContextMenu FullScreen ListType TableOperations EditTag LangMarks Abbreviation" description="When xinha is specified as richtext editor (see parameter RichTextEditor) then use the following xinha plugins per default."/>
        </parameters>

    </version>
</package>
