Well, HTML::Template is not going to make your database
searching any easier, but it will allow you to use
abstraction techniques on HTML. For example, i like to use a
'skeleton' template that encapsulates the header, footer,
and main content for a site:
<html>
<head>
<title><tmpl_var title></title>
</head>
<body>
<tmpl_include name="header.html">
<tmpl_var CONTENT>
<tmpl_include name="footer.html">
</body>
</html>
Now, that was just an example ... i don't always use that
format, but i hope you get the picture. The idea is that
you break up the "elements" of the web site into their
own files. Say you have a menu bar on the side. You can
abstract the HTML into it's own file and then simply
include that file when you need it. As long as code that
populates the params of the HTML::Template object passes
the parameters that 'widget' needs, all is well.
Here is a complete example you can play with:
One last item. A question for you. What is the
difference between two forms - one form adds a new record,
the other form edits an existing record? What is really the
only difference? The first form does not have an id - the
second does. So, if there is no id present, then the user
is adding a new record. If there is, then they are editting
an existing record. It is really not very hard to abstract
this into 3 templates: 2 skeletons (one for edit, one for
add) and a template that contains the form elements. I
leave this as an exercise. :)
Oh, and remember, sometimes it is more trouble than it is
worth to get as abstract as you possible can. You might wind
up making your interface so general that no one can easily
use it anymore. :/
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
| [reply] [Watch: Dir/Any] [d/l] [select] |