Alamgir,
Thanks for the link. I looked at the project however the overview tells
me very little:
"Rayures is a library that makes developing web applications with
Stripes even more enjoyable. The View module provides integration with
Velocity, and many conveniences, while the Test makes i
Nikolaos,
I needed to load templates from the classpath. I also needed to
process templates in a somewhat 'standalone' mode. Both were easier
with Velocity than JSPs.
I also needed a templating solution for another framework (another
language, even!) that just merged a map of key-value pairs with
Freddy,
Thanks for the reply and as you have used Velocity so much I would love
to hear:
--> At least 3 "specific" "key" reasons why "their choice" of
templating engine was selected over JSPs and built-in TLDs?
I don't just want to hear "I use templating engine X which is great
for me" OR "
On May 26, 2010, at 10:22 AM, Nikolaos Giannopoulos wrote:
> Morten et al.,
>
> OK... I'll bite... . I really didn't want this to devolve into "my choice"
> of templating engine is better, and there are many comparisons out there, but
> we are developing a large project and if I'm going to fi
On 26-05-2010 at 13:22, Nikolaos Giannopoulos wrote:
> --> At least 3 "specific" "key" reasons why "their choice" of
> templating engine was selected over JSPs and built-in TLDs?
At my work, the choice is usually made due to a simple criterion:
"Will it be used outside screen rendering?"
Morten et al.,
OK... I'll bite... . I really didn't want this to devolve into "my
choice" of templating engine is better, and there are many comparisons
out there, but we are developing a large project and if I'm going to
find the need to switch down the road better NOW than later.
With tha
