htp on-line reference : Files |
||||||||
Using default filesOften you want to use the same templates, the same options, and the same macros in all htp files in a certain project. To support this htp parses a default file that can contain the necessary template, macro definitions. It can also include other htp files.
At program start, htp will look for an environment variable called
htp will then search the current directory for a file named
"htp.def". This file, called the project default file, is
also processed like the The file "htp.def" should contain all macros, metatags (see next section), options and templates common to all files in the directory. That is, if you organize your HTML file groups in separate directories, each directory has it's own project default file with settings and macros particular to that project. The use of a global Organizing your fileshtp has been designed to break apart two components required to HTML files: design and content. This is good as it allows you to change your design without having to touch the content and to add new content without having to think about the design. The design of your pages is best kept in a template file as seen in the last section. As mentioned earlier these reference manual is also created from a template file. Page content should be held in separate files, each using Although htp does not enforce any file naming conventions, I've adopted the following file extensions for my own sanity:
So much about files. In the next section you can learn how to customize htp to your own needs by defining your own tags.
|
||||||||
|
||||||||
htp on-line reference / http://htp.sourceforge.net/ref/
Authors: Jim Nelson, Jochen Hoenicke, Michael Möller. Maintainers: Jochen Hoenicke.
Copyright © 1995-96 Jim Nelson. last updated Tue Feb 22, 2011 |