2Re: Web page template for an HTTP daemon script

Before you run off and start using your templating system on all of your HTTP daemons, ask yourself these questions:

How will be able to have conditional branches?
How will be able to loop?
How will i be able to restrict scope?
How will i be able to include other files?
How will i know when to escape certain variables?

Sure, you don't need them now ... but you will ;)

Do me a favor. Read ~~my reply~~ OOPS! my reply (hopefully) again and compare the code i submitted to your hand rolled solution above. The template itself is mostly the same, you may like your 'tags' better, but HTML::Template's have the features i listed above. The code also looks mostly the same - these are reasons to use HTML::Template ... or Text::Template. I get the feeling that you did not play around with these modules and get a real feel for them. There is nothing wrong with reinventing wheels for your own education, but there is everything wrong with reinventing wheels because you are too hasty to 'see results now'. Invest time in research, it pays big. ;)

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)

Comment on 2Re: Web page template for an HTTP daemon script

Replies are listed 'Best First'.
Re: 2Re: Web page template for an HTTP daemon script by bronto (Priest) on Aug 14, 2003 at 08:26 UTC
Hello jeffa First, thanks a lot for replying with constructive arguments: I apreciate it a lot About your comments: How will be able to have conditional branches? How will be able to loop? How will i be able to restrict scope? How will i be able to include other files? How will i know when to escape certain variables? The answer to all questions is no Read my reply (hopefully) jeffa, I read your answer, as I did with all the other ones (the right, one, not the one you linked, anyway: you missed the final digit in the ID `:-)`. Your solution is good, and mine isn't surely better, nor it is flexible. The reason why I chose an handmade solution is the footprint that my script has in memory: it's about 5300 kbytes at startup. Simply adding a `use HTML::Template`, without instanciating any object, makes it go to about 6000 kbytes... I get the feeling that you did not play around with these modules and get a real feel for them. Your feeling is right. I am an AxKit guy. `:-)` I found that it is such a great tool that I definitely abandoned any other template approach for web site management. Until yesterday. There is nothing wrong with reinventing wheels for your own education, but there is everything wrong with reinventing wheels because you are too hasty to 'see results now'. Invest time in research, it pays big. ;) Well, actually I don't like reinventing the wheels, mainly because I assume that there is someone that did the job better than me, unless the contrary is proven; in this sense, perlmonks often confirmed that my assumptions were right. Thanks again for your help `--bronto` The very nature of Perl to be like natural language--inconsistant and full of dwim and special cases--makes it impossible to know it all without simply memorizing the documentation (which is not complete or totally correct anyway). --John M. Dlugosz	[reply] [d/l]

Replies are listed 'Best First'.

Re: 2Re: Web page template for an HTTP daemon script
by bronto (Priest) on Aug 14, 2003 at 08:26 UTC

Hello jeffa

First, thanks a lot for replying with constructive arguments: I apreciate it a lot

About your comments:

How will be able to have conditional branches?

How will be able to loop?

How will i be able to restrict scope?

How will i be able to include other files?

How will i know when to escape certain variables?

The answer to all questions is no

Read my reply (hopefully)

jeffa, I read your answer, as I did with all the other ones (the right, one, not the one you linked, anyway: you missed the final digit in the ID :-). Your solution is good, and mine isn't surely better, nor it is flexible. The reason why I chose an handmade solution is the footprint that my script has in memory: it's about 5300 kbytes at startup. Simply adding a use HTML::Template, without instanciating any object, makes it go to about 6000 kbytes...

I get the feeling that you did not play around with these modules and get a real feel for them.

Your feeling is right. I am an AxKit guy. :-) I found that it is such a great tool that I definitely abandoned any other template approach for web site management. Until yesterday.

There is nothing wrong with reinventing wheels for your own education, but there is everything wrong with reinventing wheels because you are too hasty to 'see results now'. Invest time in research, it pays big. ;)

Well, actually I don't like reinventing the wheels, mainly because I assume that there is someone that did the job better than me, unless the contrary is proven; in this sense, perlmonks often confirmed that my assumptions were right.

Thanks again for your help
--bronto

The very nature of Perl to be like natural language--inconsistant and full of dwim and special cases--makes it impossible to know it all without simply memorizing the documentation (which is not complete or totally correct anyway).
--John M. Dlugosz

[reply]
[d/l]