next up previous contents index
Next: Example Up: Templates Previous: Creating own templates   Contents   Index


Templates Structure

The HTML export of the WLAN-Visualizer is based on different HTML templates, which can be defined freely by the user. To success the user has attend some things.

First we take a closer look into the "templates" directory within the programms directory. It should look like figure 5.1

Figure 5.1: The "templates" directory
\includegraphics[width=2.5in, height=1.5in]{templates_path.ps}

The "img" directory contains all the images needed, the "css" directory contains the style sheets to format the HTML page. So there are three files left. The "index.html" later becomes the start page of the export. For each floor a HTML page is created with "floor.html" and "floor_menu.txt". In "floor_menu.txt" you specify a menu structure, to link between the different floors on each page.

So how the whole thing works? Each of these files contains different tokens , which are later replaced by the dedicated information. A whole list of these tokens is listed in table 5.1.


Table 5.1: Token Overview
Table 5.1: Token Overview
Token name description
$HEADTITLE the title of the document, appears in the window title bar of the browser
$CONTENT here all information about the interpolation is placed
$BUILDINGNAME the name of the building
$FLOORMENU here the contents of "floor_menu.txt" are placed
$COUNT use this token to enable for example rollover images
$AHREF where to link to, i.e. another floor
$FLOORNAME use this to place the floor name, use only in "floor_menu.txt"
$YEAR there the date and time of the export is printed
$FLOORIMAGE there the image of the floor is printed
$TITLE the floor name is printed at this location, it's nearly the same like $FLOORNAME, but use this token as a title, use only in "floor_menu.txt"



next up previous contents index
Next: Example Up: Templates Previous: Creating own templates   Contents   Index
SWT-Gruppe 2003-07-08