I actually meant to infer that my high expectations came from the high level
of execution and utility provided by the project. Velocity rocks.
However, as Jon pointed out, I may have had expectations that you are too
high. ;-)
p.s. When I get the new Ant task working I'll see what I can to share it.
-----Original Message-----
From: Jon Stevens [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 24, 2001 2:29 PM
To: velocity-dev
Subject: Re: Dynamic Velocity Root designations?
on 8/24/01 10:46 AM, "Provencher, Samuel" <[EMAIL PROTECTED]> wrote:
> I would like to learn more about Velocity but the existing docs seem to be
> more reference than tutorial (a section on usage planning would be
valuable
> since there seems to be many ways to use it). For example, I found
> interesting, your recommendation to try to not use the Runtime classes
> directly when, after looking at some code, the Velocity code simply calls
> the Runtime. Is this to plan against code breaking as the project evolves?
I
> never saw anything in the docs that addresses the topic of who should use
> what when and how. Maybe my expectations were too high, since the project
is
> so impressive from what I've seen so far.
We aren't mind readers. So, yes, I think that your expectations that we are
are too high.
:-) :-)
> p.s. In that project I mentioned, I implemented the Velocity processsing
> piece as an ANT Task.
Great! That is exactly how we envision one of the many ways it can be used.
It is a "tool".
-jon
