Rather than serving the web pages as usual, but allowing big chunks of programming inside them (or, even worse, makng you put chunks of HTML inside your perl), HTML::Template has you create what looks like a plain HMTL file, but with a few special tags in it. Mostly just variable values, with a few rudimentary control structures thrown in. You hand HTML::Template the template, and the values with which to fill in the blanks, and your finished web page comes out the other end.
(up on my soapbox)
This is the way things should be.
Separate design and content -- in this case the code is the
content.
These boundaries let the approrpiate experts do their own jobs without having to try and learn too much of someone else's, and without tripping over each other editing the same files.
It makes life much easier down the road when either the code or the presentation has to be converted to something new.
It even works for you in the area of code reuse. Once
you've got this nice web-based application, you can easily
reuse most of that code -- virtually untouched, if you've been careful -- to function with a screen-based interface or a batch processing system or whatever someone thinks up next, just by modifying the input and output bits on the edges.
In reply to Re: Emberl anyone???
by Cubes
in thread Emberl anyone???
by costas
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |