Pretty, documented source of patXMLRenderer/overview.xml

Stephan Schmidt

</author>

<pat:getMetaNav/>

<xinc:include parse="xml" href="/nav/headernav.xml"/>

<xinc:include parse="xml" href="/nav/projectnav.xml"/>

</meta>

<randy:attribute name="maintainer">

<pat:getProjectInfo project="patXMLRenderer" info="maintainer"/>

</randy:attribute>

<randy:attribute name="developers">

<pat:getProjectInfo project="patXMLRenderer" info="developers"/>

</randy:attribute>

<randy:attribute name="version">

<pat:getProjectInfo project="patXMLRenderer" info="currentVersion"/>

</randy:attribute>

<randy:attribute name="releaseDate">

<pat:getProjectInfo project="patXMLRenderer" info="releaseDate"/>

</randy:attribute>

Randy, the patXMLRenderer, transforms XML into HTML pages (or any other ASCII Format you like) using the patTemplate class.

</introtitle>

<para>

Our website is entirely generated by Randy. The big advantage of the system is that you're not limited to static content - the patXMLRenderer system supports custom extensions that let you generate dynamic content (like database queries) directly in your XML pages.

</para>

</intro>

<body>

<main>

<para>

You should use our renderer if you'd like to separate content from layout on your website. The content is stored in XML files while the layout of your page is stored in templates. You can now easily change one of the components of the site without changing the other. It also allows you to easily switch designs or create different output formats like LaTex, HTML, PDF, WML,...

</para>

</section>

<ul>

Currently the following features are implemented:

</lihead>

<uli>

Transform any XML document (read files or strings) with a free tag set into an HTML Document (or any other format)

</uli>

<uli>

Use as many template files as you like and define the filename of the used template in your XML file

</uli>

<uli>

Uses patTemplate which allows "intelligent" templates (e.g. condition templates). This feature enables you to use one tag for a textparagraph with AND without a headline. The template engine chooses the correct template to use. Take a look at <link type="internal" url="patTemplate/overview.xml">patTemplate</link> for more information.

</uli>

<uli>

Supports use of external entities. This feature enables you to store the often used parts (like navigation or footer) in separate files, which will be included in your XML files. This feature resembles the PHP include() statement.

</uli>

<uli>

Offline Generator which lets you create static HTML pages that can be downloaded as a zip file

</uli>

<uli>

Randy automatically opens an index and error file and displays it if no file was given or the file to parse does not exist.

</uli>

<uli>

Intelligent cache functions, so a page is only generated when content or layout changes.

</uli>

<uli>

Auto cache can be overridden to force caching for a certain time.

</uli>

<uli>

Supports XSLT-like parameters which allow dynamic attribute values.

</uli>

<uli>

Customizable using extensions that are assigned to an XML namespace. These extension may create any content that will be included in the HTML document. The extensions may also return XML content which will be transformed by Randy.

</uli>

<uli>

Several extensions are included which handle commonly needed tasks like database queries, time functions, file access and more...

</uli>

<uli>

Easily switch between skins (different layouts)

</uli>

<uli>

Extensions may be "stacked", you may use the tag of an extension between the opening and closing tag of another extension. You could use this feature to create a dynamic database query, which returns a database result.

</uli>

<uli>

Automatic logging. Randy will create a daily log which can be used to create access statistics. As Randy is able to add URL parameters to all internal URLs PHP Session Management can be used to track unique visits.

</uli>

<uli>

Referer and error log.

</uli>

<uli>

Administration area that lets you view logfile analysis of access and referer log.

</uli>

<uli>

Help on all installed extensions in the administration area.

</uli>

<uli>

Supports <link type="internal" url="/about/patExtrasOverview.xml">patExtras</link> to ease the communication with the php-tools.net team.

</uli>

</ul>

</section>

<para>

Take a look at the <link type="internal" url="patXMLRenderer/todo.xml">Todo list</link> if you'd like to known what we are planning for future versions.

</para>

</section>

</main>

<xinc:include href="/misc/inc_partnersites.xml"/>

</sidebar>

</body>

</page>

</document>