A multi-language content generation module... I can hardly think of a
such a beast, but I could be a stubborn conservative.
It would work if content generation modules worked like filters,
outputting down the filter chain for the other module to parse their
embedded code. I make out dreadful problems ahead and uncertain
benefits, considering also the many alternatives you have today.
-- Massimo
On 2012-07-23 6:08, Nagarajan Chinnasamy wrote:
This point leads me to the imagination of having a template that has
all different things embedded (xml, tcl code, php code etc.). This
may
need a super-template-processing-module as an apache module that
dispatches a <?xxx block to the right template-processing-module
based
on configuration directives.
Best Regards,
Nagu.
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
