Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <4119D7F6.7040606@mobilebox.pl>
Date: Wed, 11 Aug 2004 10:25:26 +0200
From: Leszek Gawron <lgawron@mobilebox.pl>
User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: why JXTG sucks? was: FreeMarker integration
References: <802926B6AB8533408C33ADBCA3EE5C2A138BED@coso.staff.vuw.ac.nz>
 <4119D236.7050808@mobilebox.pl>
 <573FC1EC-EB6E-11D8-BE1E-000A95DC4186@apache.org>
In-Reply-To: <573FC1EC-EB6E-11D8-BE1E-000A95DC4186@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Ugo Cei wrote:

> Il giorno 11/ago/04, alle 10:00, Leszek Gawron ha scritto:
> 
>> - I end up inserting a wiki parser in user session and referencing it 
>> in jx template via:
>> ${cocoon.session.wikify( activity.task.project.description, 
>> cocoon.consumer) }
>> Same for any other formatter or presentational macro (like link 
>> decorator)
> 
> 
> A possible solution would be to write a WikifyingTransformer and put it 
> after the JXTG in the pipeline. Wouldn't this be cleaner or am I missing 
> something?
> 
>     Ugo
> 
fine for a single formatter, a nightmare if you end up with 10 or so. 
Even with one you have to be sure to transform your every view with your 
new transformer.

And what about performance issues? Wouldn't this slow rendering down?

-- 
Leszek Gawron                                      lgawron@mobilebox.pl
Chief Technology Officer                           MobileBox sp. z o.o.
+48 (61) 855 06 67                              http://www.mobilebox.pl
mobile: +48 (501) 720 812                       fax: +48 (61) 853 29 65