I've been following the Velocity and Tubine projects closeley for
more than 6 months. I developed a template heavy application
(having the controller code also coded as templates!) using
turbine and WM.
Last week I ported everything sucessfully to Velocity. It emits
much cleaner error messages (some bugs in the file/line names
in the log) and feels faster. I submitted some patches to make
the automatic conversion from WM to Vel complete. I hope the
patches are ingested by now. So if you take the nightly build
(from tomorrow the 2001-01-16) you could make a smooth
transition. Note that any Java screen code must also take
minimal changes on the imports and inheritance.
I have the feeling Velocity is now almost mature for a release.
I will be sending patches to fix anything that does not yet
work correctly (e.g. error log messages).
If you use the TDK to create the base application, copy the
new velocity_XXX.jar into the WEB-APP/lib together with your
converted templates and java files into it, you should be up
and running quickly (within 1 hour if you are an ace).
You will the profit directly from the Admin application coming
up....
:) Christoph
Gergely Timar wrote:
>
> Hello everyone!
>
> We've started a project using Turbine and the Webmacro template
> engine and I was wondering if we had anything to gain (license
> differences aside) by switching to Velocity? I understand that the
> todo list points on Velocity on the website were outdated, but how far
> has the Velocity project come? Also, what steps would have to be
> taken to make the switch?
>
> --
> Thanks,
> greg mailto:[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
