> From: Sean Legassick [mailto:[EMAIL PROTECTED]]
>
> > Yes, but Texen could [and should] be an independant utility ?
>
> I'm not sure that makes sense - Texen works as a layer on top of
> Velocity, so it can't be Velocity independent. And its util
> classes are specifically designed to be used within Texen templates (which
by
> definition must be VTL templates).
Ok. I haven't used Texen, so wasn't sure if the utils would also be
accessed outside of the templates, from Java code.
> > If that's the case, I think it's utility interfaces should provide the
most
> > flexibility and not be tailored just to work with Velocity.
> >
> > I don't really have any strong feelings about this - just thought it
would
> > make Texen more general and useful.
>
> Well I have no strong feelings either other than that the StringUtil
> class packaged with Texen should work with Texen :-) :-)
Yep.
> So feel free to either commit my patch or make your change instead
> (which is actually less of a code change)...
Ok. It will be done.
I think we have reached an impasse of apathy. :) Your patch would be fewer
keytrokes :)
geir
