[EMAIL PROTECTED] wrote:
> I also understand that velocity is being built in to turbine and there would
> not be much difference between webmacro and velocity except that the parser in
> velocity is efficient (is it right ?).
Velocity has a good chance to turn out to perform faster, once it's
ready
and optimized (the benchmarks results are to say the least optimistic).
The issue with parser was mainly flexibility and mainatinability.
> My question is would webmacro be removed from turbine once the velocity is
> built in completely ? if so, How much work it would be to convert webmacro
> site model to velocity ?
Now that the licence issues have been sorted out, there is no real need
to
remove WebMacro support from Turbine. It will be probably left in place
for anyone who whishes to use it.
Converting from WebMacro application to Velocity should be trivial.
Templates
can be converted with an automated tool (regexp based), and some things
will
need to be configured differently in TR.properties.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
