> Basically, I'm stuck. I'm keeping MyVeloctity-1.2 as is, becuase we have > users using it and *shock* documentation on how to use it. There's code > being made now against this new model, but that doesn't mean that all is > lost for the rest of you. Run, while you still can! > > Sorry to cause such a fuss. I'll shut up now.
Just wanted to say that if I would build a new TemplateParser from scratch I would use a model like that one you describe. But I can also understand that the velocity team wanting to keep things simple and repect them for that. I have seen template systems migrating from just a template handling into script languages of their own. My own opinion is that enabling math and compare expressions with floats is in the danger zone but in my world I would implement it :). As a matter of fact I began writing a TemplateParser form scratch last weekend and I got a working version now ;). It supports int, long, float and double number I guess in a way similar to your implementation. But since a 10 day old application can't be called mature I will not release it yet. I am still doing API changes on a daily basis. I have been happy with Velocity and still am, but I couldn't get multipass parsing working as I wanted. Therefor my little project :) You can take a look at the "current" API here http://nyx.obidobi.net/~thomas/speed/ In a month or two it might be a usable complement to Velocity Thomas �hl�n > Best Regards, > > Will Hartung > ([EMAIL PROTECTED]) > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
