> I'm curious about one thing: How easy is it to do fill-out forms
> with pipelining templating systems like AxKit? I'd think that in
> such cases the stylesheet would have to do so much work that it
> would become, in essence, like a CGI script.
Can you explain what work you're talking about h
>
> > But then if you're happy with EmbPerl, why switch?
>
> A couple of reasons, really:
>
> 1) well, I actually wouldn't switch per se; people think in
> different ways, and it's often useful to support (and feel
> comfortable with) different development paradigms
>
Embperl 2.0 (sta
> -Original Message-
> From: Richard L. Goerwitz III [mailto:[EMAIL PROTECTED]]
>
> Is AxKit the best of the pipelining breed, though? (I personally
> am finding XML to be a ghastly, ugly thing; it all started with
> namespaces, which are implemented via attributes in a horribly
> kludgy
Matt Sergeant wrote:
> But then if you're happy with EmbPerl, why switch?
A couple of reasons, really:
1) well, I actually wouldn't switch per se; people think in
different ways, and it's often useful to support (and feel
comfortable with) different development paradigms
2) EmbPe
I tend to use PerForm for complex forms:
http://theoryx5.uwinnipeg.ca/CPAN/data/AxKit-XSP-PerForm/PerForm.html
Others write custom taglibs:
http://theoryx5.uwinnipeg.ca/CPAN/data/AxKit/Apache/AxKit/Language/XSP/Tagli
bHelper.html
The general idea is that the output is an abstract representatio
