cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leszek Gawron <>
Subject Re: [RT] StringTemplate: The answer to our templating needs?
Date Fri, 29 Oct 2004 11:05:17 GMT
Bart Molenkamp wrote:
>>-----Original Message-----
>>From: Carsten Ziegeler []
>>Sent: Friday, October 29, 2004 10:47 AM
>>Subject: RE: [RT] StringTemplate: The answer to our templating needs?
>>Bertrand Delacretaz wrote:
>>>I don't think JXTG is broken now, it works well but the code
>>>is hard to understand and having all classes in a single huge
>>>source code file does not help.
>>Yupp, that is one of the problems with JXTG. It would be great if
>>a new solution would be pluggable to add new "tag libs" as well.
> Making it pluggable may also have the disadvantage that languages are
> added that can give more control than required for presentation of data.
> This can make the separation of concerns less clear, which is IMO one of
> the great things in Cocoon (the control flow). Templates may look like
> XSP pages, or similair (code mixed with content), breaking the SoC.
You are right the SoC might be broken easily. Still you can code your business 
logic in flow. It's not elegant but you can. Same goes for templating 
languages. You shouldn't break SoC but you can. That won't kill you. That's 
how I started using cocoon. After a few projects you realize yourself that XSP 
  does not work for you and you try to make the project be more elegant. You 
are ready for more advanced approach.

It's like driving a car: a car has a power to go 200 km/h. Still you are being 
taught not to drive at that speed. You should be able to do a lot with your 
templating language but be advised to do it in some commonly agreed manner.

Leszek Gawron                            
Project Manager                                    MobileBox sp. z o.o.
+48 (61) 855 06 67                    
mobile: +48 (501) 720 812                       fax: +48 (61) 853 29 65

View raw message