Today I wanted to expand my knowlegde ... "to seek out new template life".
I tested "patTemplate" and it works fine. It has no "setdbloop".
"Ok," I thought. "Nice to have but not really necessary."
A real set back: If you include (tmpl_include) other templates, you are not allowed to have tmpl_var's in them! :evil:
At this point "patTemplate" was out of business.
---
"smarty" was even worth. I tried half an hour to get it to work.
Note: I do not want to change my PHP.ini for "smarty" best result was:
/usr/local/www/htdocs/vlib/smarty/
Warning Smarty error problem creating directory /%%-83/%%-835172124 in /usr/local/www/htdocs/vlib/smarty/Smarty.class.php on line 1043
Warning Smarty error problem writing temporary file '/%%-83/%%-835172124/3ee07adf2a79d' in /usr/local/www/htdocs/vlib/smarty/Smarty.class.php on line 1043
Warning unable to create file /%%-83/%%-835172124/smarty_basic.htm.php because No such file or directory in /usr/local/www/htdocs/vlib/smarty/Smarty.class.php on line 1576
Warning Failed opening '/%%-83/%%-835172124/smarty_basic.htm.php' for inclusion include_path='./usr/local/lib/php' in /usr/local/www/htdocs/vlib/smarty/Smarty.class.php on line 1159
I tried typing the path manually, moved the tmpl-file in the same dir as the PHP script => nothing worked.
---
Now I think: I gave both a fair chance and perhaps create docu about the two classes, so users in Germany could have a choice.
Whatever I try with vLIB, it's easy.
require_once "vlibTemplate.php" => works.
I do not have to configure any config.inc's or so.
setdbloop => works. No brain needed if I want a quick output of mysql data.
vlibTemplateDebug is very great, too.
...
Why bother with smarty or patTemplate?
The vLIB fan
