AW: Velocity versus pure XSLT

[Merico Raffaele <ra...@less.ch>]

Dear Bertrand

First of all, sorry for the long interrput. When I got your email I was in
vacation until today. 
2) thanks a lot for your tips
3) Yes, we are willing to share our know how on style-free XSLT style
sheets. I just want to remember, that our contribution has a main focus on
XSLT and therefore I'm not sure if this is the right place for it. Reflect
it and tell me if it's OK.

Raffaele Merico
LESS Informatik AG
Böhnirainstrasse 14
CH-8800 Thalwil

Tel: +41 1 723 12 22
Dir: +41 1 723 92 45
Fax: +41 1 723 12 23

mailto:merico@less.ch


-----Ursprüngliche Nachricht-----
Von: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]
Gesendet: Donnerstag, 30. September 2004 12:20
An: users@cocoon.apache.org
Betreff: Re: Velocity versus pure XSLT


Hi Raffaele,

> ...Finally I have implemented my own application specific
> template language that separates XSLT from (X)HTML/FO. The XML 
> templates
> (i.e. XHTML or FO) use $Vars for the value bindings and <my:tags/> for 
> logic
> steering. Now this (X)HTML templates can be edited with a 
> WYSIWYG-Editor
> like Dreamweaver...

Sounds interesting - this might be a nice contribution or example for 
others, would you be willing to share this?

You could either write an article on the wiki or, submit a patch with 
samples of what you've done.

> ..In the mean time I have written some XSP-Pages and combined
> them with above described XSLT template solution. This solution works 
> fine
> if all the data is in the XML stream. But now I'm asking myself, if 
> Velocity
> or another template language would be better. Especially if beside the 
> XML
> data there is also some information stored in the session that must be
> processed..

Note that XSP is not recommended for new applications, if you're 
starting you should rather use Flowscript and the JXTemplate generator, 
for example. You can find an overview of this in the "tour" block, 
accessible from a link on the samples page once you've started Cocoon.

Velocity is a nice templating language but I don't think it makes a 
difference in terms of combining multiple data sources: the usual way 
to combine data in Cocoon is to convert it to XML via a generator, and 
to aggregate several XML flows with <map:aggregate> or the with the 
CInclude transformer.

Hope this helps!

--
   Bertrand Delacretaz
   independent consultant, Lausanne, Switzerland
   http://www.codeconsult.ch



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: AW: Velocity versus pure XSLT

[Bertrand Delacretaz <bd...@apache.org>]

Hi Raffaele,

> ...3) Yes, we are willing to share our know how on style-free XSLT 
> style
> sheets. I just want to remember, that our contribution has a main 
> focus on
> XSLT and therefore I'm not sure if this is the right place for it. 
> Reflect
> it and tell me if it's OK..

I think XSLT is a big stumbling block for many people when starting 
with Cocoon, yet learning it is very worth the effort.

So I'd say yes, if your stuff can help people use XSLT more efficiently 
in Cocoon, I'd be +1 on finding some space for it in one of our blocks, 
even if it's "just" as a sample.

So maybe the best thing would be, when you find some time, to package 
the simplest sample that you can think of, and submit it as a patch so 
that the committers can decide on a concrete basis. But IMHO good 
samples and best practices examples are always welcome.

-Bertrand