>Does it not work for you to do it all in your script, something like..
>
>foreach my $key (keys %HoH) {
> foreach my $key2 (keys % {$HoH{$key} }) {
> push(@results,"<a href=\"$key\">$key2 <!-- Hidden ID:
>$HoH{$key}{$key2}--></a>");
> }
>}
>$template->param(RESULTS => "@results");
>
>Then in the template
><H3><TMPL_VAR NAME="RESULTS"></H3>
>
>I know its a little html in the script, unfortunately.
Agreed, it is unfortunate. This bit of code, to me, goes against everything
that HTML::Template is about: Separating functionality from presentation.
Consider this: What if you were coding a website and had a designer working on
the look of the site? For him/her to apply a particular style/font/image to
this anchor tag, they would need to go into the code to do it. Bad, bad. :)
Generally, HTML::Template offers the things you need to get the job done and
done in the paradigm that H::T uses. die_on_bad_params is the only logical
choice here. It has no adverse side-effects, either.
--Joel
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Html-template-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/html-template-users
