I few years ago, I was very excited about using XSLT and still think it is
pretty cool, but I found XSLT to be very akward for certain logical
evaluations and designers had a hard time picking up the transformation
language. The learning curve for designers seemed much higher than using
templating systems like Velocity. Other could have opposite experiences, so
I'm not sure if it really does have a higher learning curve. I also know my
direct experience is not a good indicator of the learning curve because I
will pick up a templating language like Velocity much quicker, because it is
well... for a lake of a better phrase... very Java like.
When it comes to XSLT vs. Velocity, I feel Velocity has more pros and cons
relative to XSLT for my projects, thus I will most likely stick with
Velocity if I had to use one or the other. If you guys can figure out a way
to take advantage of the pros each, that would be wonderful. In one extreme
it could be a simple as using Velocity to create XSLT stylesheets and use
Velocity for some of the difficult evaluations, but it might not be that
simple. I have not really thought much about it, or how it would work, but
it seems like it would be very cool.
