On Tue, Apr 16, 2002 at 12:40:13PM +0100, [EMAIL PROTECTED] wrote: > At the moment I can fake it using a super-ugly kludge
Hmmm.... maybe the suggestion to pre-tranform your templates will be the easiest to implement. You could set ttree to point to your existing template tree, having it process all files to a new location using a PROCESS template which does something like: [% PROCESS $template FILTER my_transformer %] If you set TAGS to be something different from usual (e.g. TAGSTYLE star) then any regular [% ... %] TT directives will get passed through intact. Anything you want processed during this first pass can be put inside a [* ... *] directive. Your my_transformer code has to ignore anything in a [% ... %] which you want passed through intact, and should just process the regular text blocks. It shouldn't be too hard to have it recognise something like '<input foo="bar">' and convert it into '[% input(foo="bar") %]' or whatever the TT equivalent is. Presumably you could modify the parser/generator of your existing template system to spit out the TT equivalents for your existing directives. Then your new set of templates should run natively in TT. You could even continue to develop templates using your old syntax and simply re-run ttree to convert them into new form for "runtime". A
