where to start with new template component?

[Georg Kallidis <ge...@cedis.fu-berlin.de>]

Hello,

I am a little bit at a loss concerning the following case and hopefully
not missed the whole point, but:

If I would like to integrate another templating mechanism (e.g. Jade)
instead of or parallel to e.g. Velocity, where would I start? (not that
I actually would do this right now, but just in case)..

There is an old Howto (Template Service) mentioned in the Fulcrum
project webpage*, and another template related link**; in the VCS/SVN I
find a copy of JSP and Velocity Service (fulcrum-template) - but these
classes (package org.apache.fulcrum.template) have sister classes e.g.
in package org/apache/turbine/services/velocity in the default turbine
module (AND the latter classes are more up-to-date, e.g.
TurbineTemplateService compared to the same class in the other package).

It seems to me, that integration of the templating mechanism as a Yaafi
component is not the way to go... Was it a design decision in the past,
NOT to integrate the templating services into Yaafi? Then may be IMO
fulcrum-template should be removed (may be I missed the right place).

So, my question is: Would I hook in the existing (Yaafi) component
fulcrum-template (I do not use it at the moment) or just better look at
the classes in package org.apache.turbine.services?

Thanks,
Georg


* http://turbine.apache.org/fulcrum/howto/template-service.html
**  http://turbine.apache.org/fulcrum/fulcrum-template, which currently
points to the BSF component. BTW: The example shows, how it would be
used as a fulcrum-yaafi, but I cannot find the class TurbineBSFService
only DefaultBSFService.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org

Re: where to start with new template component?

[Thomas Vandahl <tv...@apache.org>]

Hi Georg,

On 25.03.2013 17:24, Georg Kallidis wrote:
> If I would like to integrate another templating mechanism (e.g. Jade)
> instead of or parallel to e.g. Velocity, where would I start? (not that
> I actually would do this right now, but just in case)..
That would be very welcome.

> So, my question is: Would I hook in the existing (Yaafi) component
> fulcrum-template (I do not use it at the moment) or just better look at
> the classes in package org.apache.turbine.services?

The general idea of the Fulcrum components was to make them available to 
use-cases outside of Turbine. Right now, the template-service is rather 
tightly coupled to the Turbine module concept. This is not to say that 
such a templating service could not be useful outside of Turbine. It 
would just need a lot of generalization of the interface to make that 
happen. If you want to invest that effort, I'll be fine with it. If not, 
I'm fine, too.

Bye, Thomas.

PS: Please be aware that the Fulcrum component has not been updated with 
the patches that went into the TurbineTemplateService for a long time.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org