I'm not going to disparage any of the other templating systems but since
noone has chimed in for HTML::Mason, I guess I'll have to. Important
aspects of such a beast is componentization, not just "mail merge"
behaviors.
Mason components can be just HTML (or XML or fooML) or just Perl or both.
The "heavy lifting" can be moved to the bottom of a page so you can get
away from top to bottom processing whih generall demands expressing
complex code in the middle of HTML. Caching by distilling components down
into Perl code. In many other respects, the API, the execution and the
object models are the most empowering.
My current focus is on using Mason as a component system but XSLT when I
need ad-hoc transformation a la AxKit, Cocoon and other XSLT
processor-based systems. Mixing AxKit and Mason may sound crazy but each
has compelling ideas in their architecture.
As far getting Zopely with mod_perl tools, in my talk in the Apache track
about the publishing and content management at Salon I discussed getting
there last week in Monterey.
Today, Erich L. Markert <[EMAIL PROTECTED]> frothed and gesticulated about...:
> OK, I'm nearing the end of one project so I'm able to take a look at new
> solutions so one question comes to mind. What does the template toolkit
> offer above and beyond HTML::Embperl or some other templating solution?
>
> On a side note, wouldn't the mod_perl community be better served
> focusing on one of these solutions and building upon it and creating a
> mod_perl based application server much like Python has Zope?
> --
> __________________________________________________________
> Mr. Erich L. Markert [EMAIL PROTECTED]
> Computer Learning Center TEL (914)422-4328
> Pace University
> 1 Martine Ave
> White Plains, New York 10606-1932
>
> Those who do not understand Unix are condemned to reinvent it, poorly.
> -- Henry Spencer
>
--
Salon Internet http://www.salon.com/
Manager, Software and Systems "Livin' La Vida Unix!"
Ian Kallen <[EMAIL PROTECTED]> / AIM: iankallen / Fax: (415) 354-3326
