> Now my question... what do you folks think? Am I
> being too stubborn here, or should I learn the CGI on
> form writing? Maybe it would just be easiest to
> design my forms in DW and then set them into H::T? Is
> this recommended? What are the pros and cons of this
We are here because we have the option to design our forms (as many times
for each business-logic component if we use CGI::Application) directly in
HTML templates. Thus, we can use CSS & XHTML to make our forms _standard_
or we can make up some other method to make them look however we want.
Heck, if you want to use <font /> and <blink /> tags, I do not care.
HTML::Template won't either.
As for my opinion, I do not really care what the designers use. I think
some of ours are using DW right now ... but I've made my very best sites
with VIM. That is the beauty of H:T.
As for the other question, about multiple templates, you can either do as
Kenny said and use includes (investigate options to ->new( ) for clues on
how to really control these) or use a code construct like this :
my $head = $self->load_tmpl("head1_tmpl.html");
my $body = $self->load_tmpl("login_tmpl.html");
my $foot = $self->load_tmpl("foot1_tmpl.html");
my $output = $head->output( );
$output .= $body->output( );
$output .= $foot->output( );
== this is from a CGI::Application ... 'load_tmpl( )' eventually gets around
to calling the HTML::Template->new( ) method. I used to use includes, but
Get latest updates about Open Source Projects, Conferences and News.