"Geir Magnusson Jr." wrote:
> > I guess I still don't use Veloctiy in production environment for a
> > reason.
>
> What reason, and what do you use?
> If you are being honest about your sentiments, you can't use WebMacro
> either, because they can't even seem to decide on their syntax... they
> just added a new parser and are deprecating their old one. Enjoy.
Actually, I use neither. I stay on the code side of things, and for the
most part I'm just developing the core modules of our systems, and
developing Turbine.
The web people in my team use WebMacro. We don't follow the latest and
greatest version of WM, we just use the version that is bundled with
Turbine. It has it's bugs and limitations. (Like limitation on #if
nesting depth). We know them and we live with them ... for now.
We'll be very happy to switch to Velocity for our upcoming OneWebNG
project. Our designers already already played a little bit with Velocity
and liked it a lot.
It just makes me worried, that parser problems still keep showing up.
I'm affraid that we'd get tons of Velocity related issues if we
start to use it at a large project. For example http://pfm.pl has
1.8MB of WebMacro markup in 450 files and http://www.wbksa.pl has
1MB in 300 files. We started those before Velocity was available,
and we aren't going to port them just right now...
Please don't take me wrong. We'd love to use Velocity, but we are
anxious how it will work for us.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
