Changeset 5333

Show
Ignore:
Timestamp:
09/01/10 16:02:28 (17 months ago)
Author:
mtld
Message:

updated docs

Location:
branches/release-0.15.x/pustefix-docbook/src/docbkx/reference
Files:
4 modified

Legend:

Unmodified
Added
Removed

  • branches/release-0.15.x/pustefix-docbook/src/docbkx/reference/advancedtopics.xml

    r4443 r5333  
    237237          <listitem>if you're specifying <literal>part</literal> and <literal>module</literal>, the include is loaded from the href/path of the current file from within the specified module</listitem> 
    238238        </itemizedlist> 
     239      </note> 
     240      <note xml:id="advanced.dyninclude.modinclude.special"> 
     241        <title>Special module names</title> 
     242        If you want to explicitly reference an include from the application, you can use the special module name <emphasis>webapp</emphasis>, which indicates 
     243        Pustefix, that it shouldn't look in the current module as done by default, but load the file from the webapp folder. 
     244        If you want to explicitly reference an include from the module where the page is defined (where the config fragment with the <literal>standardpage</literal> definition resides), you can use the special name <emphasis>pagedef</emphasis>. 
    239245      </note> 
    240246      <para> 

  • branches/release-0.15.x/pustefix-docbook/src/docbkx/reference/configuration.xml

    r5144 r5333  
    15581558              tags.</td> 
    15591559            </tr> 
     1560            <tr> 
     1561              <td><literal>module</literal></td> 
     1562              <td><emphasis>Optional</emphasis>. 
     1563              Specifies the Pustefix module where the file is located (by default 
     1564              the file is searched in the webapp itself).</td> 
     1565            </tr> 
    15601566          </tbody> 
    15611567        </informaltable> 
    … …  
    17021708              configuration tags.</td> 
    17031709            </tr> 
     1710            <tr> 
     1711              <td><literal>module</literal></td> 
     1712              <td><emphasis>Optional</emphasis>. 
     1713              Specifies the Pustefix module where the file is located (by default 
     1714              the file is searched in the webapp itself).</td> 
     1715            </tr> 
     1716 
    17041717          </tbody> 
    17051718        </informaltable> 

  • branches/release-0.15.x/pustefix-docbook/src/docbkx/reference/reference.xml

    r5212 r5333  
    5757   
    5858  <xi:include href="preface.xml" /> 
     59  <xi:include href="news.xml" /> 
    5960  <xi:include href="installation.xml" /> 
    6061  <xi:include href="architecture.xml" /> 

  • branches/release-0.15.x/pustefix-docbook/src/docbkx/reference/xslt.xml

    r5001 r5333  
    526526              <td>module</td> 
    527527              <td>optional</td> 
    528               <td>Not set by default. Set this to the name of the module from which the part should be loaded. If dynamic search is set, the module just serves as fallback location if the part can't be found in the project or common location and isn't overrided by another module. See <xref linkend="advanced.dyninclude"/>.</td> 
     528              <td>Not set by default. Set this to the name of the module from which the part should be loaded. If dynamic search is set, the module just serves as fallback location if the part can't be found in the project or common location and isn't overrided by another module. See <xref linkend="advanced.dyninclude"/>. You can also use one of the pre-defined special module names (see <xref linkend="advanced.dyninclude.modinclude.special"/>).</td> 
    529529            </tr> 
    530530          </tbody> 
    … …  
    599599              <td>module</td> 
    600600              <td>optional</td> 
    601               <td>Not set by default. Set this to the name of the module from which the part should be loaded. If dynamic search is set, the module just serves as fallback location if the part can't be found in the project or common location and isn't overrided by another module. See <xref linkend="advanced.dyninclude"/>.</td> 
     601              <td>Not set by default. Set this to the name of the module from which the part should be loaded. If dynamic search is set, the module just serves as fallback location if the part can't be found in the project or common location and isn't overrided by another module. See <xref linkend="advanced.dyninclude"/>. You can also use one of the pre-defined special module names (see <xref linkend="advanced.dyninclude.modinclude.special"/>).</td> 
    602602            </tr> 
    603603          </tbody> 
    … …  
    682682              <td>module</td> 
    683683              <td>optional</td> 
    684               <td>Not set by default. Set this to the name of the module from which the image should be loaded. If dynamic search is set, the module just serves as fallback location if an according image can't be found in the project or common location or another overriding module. See <xref linkend="advanced.dyninclude"/>.</td> 
     684              <td>Not set by default. Set this to the name of the module from which the image should be loaded. If dynamic search is set, the module just serves as fallback location if an according image can't be found in the project or common location or another overriding module. See <xref linkend="advanced.dyninclude"/>. You can also use one of the pre-defined special module names (see <xref linkend="advanced.dyninclude.modinclude.special"/>).</td> 
    685685            </tr> 
    686686            <tr>