"Schnitzer, Jeff" <[EMAIL PROTECTED]> writes:
> Velocity produces text that must be parsed to perform XSLT transforms.
> This new approach starts immediately with SAX events. Unlike a
> hypothetical "saxify", it doesn't require fully navigating the source
> object graph. Cool.
yes, I think so t
Velocity documents are "mostly" xml-safe. There are a couple bothersome
issues like relational operators < > and the occasional use of quotes.
Velocity produces text that must be parsed to perform XSLT transforms.
This new approach starts immediately with SAX events. Unlike a
hypothetical "saxif
I recently had reason to develop a new view type for Maverick, and
wonder if there might be any interest in it. If so, perhaps I can
contribute it back to the project.
The problem: I needed a very simple X?HTML template system. It had to
be something that, however, complicated under the hood, c
Velocity does not care what type of file it just parses text the input
and out put file can be anything you want xml, xhtml, html, htm, jsp,
txt, vm, css, xslt .
You can do everything xslt can do and much more in a far more concise way
cheers pb..
Eelco Hillenius wrote:
because that would n
