It seems that this
has been debated to death, but I thought that I would try to bring into the
picture the view of (at least) one developer (and company) that isn't as
interested in modifying or developing Turbine, WebMacro, Velocity et al.
as in using them to create an application. We are only 3 weeks away from
delivering a major product using Jetspeed/Turbine as the framework and you guys
aren't helping me at all at this point. Currently we are dependent on
WebMacro for templating in our code base. My biggest issue has been the
licensing issues with WebMacro that have prevented us from shipping our product
which uses them. Now it seems that Justin would like to fix that
(belatedly). However much I agree that its a little late in coming, it is
a fix and gives me something to go on until Velocity is ready. At this
point, I am not counting on Velocity at all as no dates have been published
(AFAIK) about when a production ready release will be ready. WebMacro
(despite its so-called bad parser) is a useable option and I would not like to
see it's integration removed from Turbine as I will simply have to reimplement
it. I would avoid making this change until Velocity becomes a viable (i.e.
production ready) alternative. Anything else is simply a hinderance to the
ready acceptance of Turbine as a viable framework.
Christian
Nichols
Director of Product
Development
Q Strategies,
Inc.
