> > How long do you think would this last? I could wait for
> about 3 hours or so
> > ;-)
>
> Well... longer than that. But even if I wrote something this
> afternoon -
> you still wouldn't learn it very quickly.
No stress here please. If you do something then send it to me and I will
take a closer look at it.
> > The problem with many templating systems is the fact that
> they invent a new
> > language like "<td>$variable</td>" which is usually not
> displayable in the
> > Browser so that the designer and the programmer must work tightly.
>
> Thats a problem with _all_ template systems, including XMLC.
> With XMLC's
> method you still have problems with bits that get conditionally
> included. Sure, looping rows of tables look good, but wait
> until you start
> using XMLC a lot. Then you'll find the flaws.
As I said: One problem with enhydra is that the id "x" is a <tr>.
> Better to start with a standard that you can build on, like
> XSLT, IMHO.
Sure.
> > What other templating systems do exists that are usefull?
>
> Thats a huge question, here's a few:
>
> EmbPerl -> mixing of HTML and logic
> Template Toolkit -> will take a look at it right now
> Apache::ASP -> nice (session management), but still mixing
> HTML::Template -> own language
> XSLT
> XPathScript (part of AxKit, which can also do XSLT) -> will take a look at
AxKit
> Mason -> AFAIK mixing
Comments start with ->
...darko
