Hi,
had problems with one of the example modules.
XML::Parser::Expat was needed, but I got only version 2.27 of expat.dll . The
version on cpan has no dll. only the pm files, they are version 2.30, but
dom.pm, another module, which requires XML::Parser, requires at least
version 2.28. S
Sure, the more templating engines the better! :-)
The only caveat here is that I definitely don't have the time to implement this,
and besides, I don't know ASP. Andy Wardley sent me a big patch to enable
Template Toolkit support, so if somebody wants to take a whack at this and send
me a corresp
"Kulp, David" wrote:
>
> I must admit that there's nothing that's really "it" in CPAN. A few months
> ago I spent a lot of time looking through the modules that Joshua described
> and never found what I wanted. I didn't know about phpLens until now, but
> it looks sweet. Instead, I've been wri
> A typical page, foo.html, contains:
>
>
>
>
> Welcome back, <%= $Session->{'username'} %>!
>
>
>
>
>
>
Glad its working out!
Looking at your solution, I think I would probably do
something more like:
Welcome back, <%= $Session->{'username'} %>!
Actually, using asp includes for the templating sounds great... I
haven't looked at the code, but I wouldn't think it would be that hard
to add. It'd be great not to have to learn yet another pseudo-language
to accomplish this (Template::Toolkit or HTML::Toolkit) when Apache::ASP
is something I
Joshua Chamas, you're my hero.
The key, of course, was the Script_OnStart event. Declaring %var
there made $var{'TITLE'}, $var{'HEADER'}, $var{'BODY'}, etc.
available to the page, its template, and its includes. You're a
life-saver!
For those curious, we ended up with the following:
global.asa
At 11:27 PM -0800 21/3/02, Jim Helm wrote:
>Looks like CGI::FormBuilder/Template::Toolkit combined with
>DBIx::Recordset is probably my best bet.
Getting more off topic now, but thought I'd mention about FormBuilder...
I find CGI::FormBuilder really useful and have come to prefer it to
use CGI
