Rather than sniping, how about some concrete ideas for what you'd like to
see next? Or better yet, since you are hanging out in the developer list,
some test cases or patches?
I have a few ideas, but I don't know how to implement them :). The "obvious"
need
of something does not imply the ability to implement it :).
E.g. one that might help improve the performance of Velocity would be a "velocity2Java" compiler,
something that could be run like the JSP compiler. AFAIK the big part of performance gain
of JSP in the last few years come exactly from this corner.
It would be a fantastic gain if for a first version the compiler:
- would work only off-line, so not at runtime like the JSP one, so only
"pre-compile".
- would be able to convert only part a of the templates (e.g. those pretty static and with big
contexts), so not 100% coverage.
At least these "generated" Java files would be than easier to profile than the Velocity engine +
templates.
Well, just an idea, but I really don't know if it's feasible for Velocity.
Ahmed.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
