Ron Pero wrote:
>
[cut]
>
> * Place the templating systems into a spectrum of categories, from simplest
> to most complex/developed.
> It would look approximately like this (not attempting to be complete):
> -Level one, simplest
> * Simple tag/anchor replacement
> * Embedded code evaluation
> -Level two, complete templating, but templating only
> * HTML::Template
> * Template Toolkit
> * HTML - Tree (??)
> -Level three, templating plus (added features such as session management,
> database integration, etc.)
> * Apache::ASP
> * Embperl
> * HTML::Mason
> * AxKit
>
Perhaps the other dimension could be whether it is based on browsing a
page that calls Perl, or invoking a Perl script that brings in a page.
Then you'd have a nice 2D grid that I would think would impart a lot of
information at a glance. Not that there aren't products that would go
into more than one cell.
Another thing to note would be whether the product is useful for
generating static pages, like Template Toolkit, and (I'm sure) others.
