Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Date: Tue, 2 Dec 2003 15:12:51 +0100
Subject: Re: coping with XSLT
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: Bertrand Delacretaz <bdelacretaz@apache.org>
To: users@cocoon.apache.org
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20031202140305.71414.qmail@web41905.mail.yahoo.com>
Message-Id: <9D4123A6-24D1-11D8-9DBB-000393CFE402@apache.org>

Le Mardi, 2 d=E9c 2003, =E0 15:03 Europe/Zurich, Timothy Larson a =E9crit =
:

> --- Bertrand Delacretaz <bdelacretaz@apache.org> wrote:
>> I've been (wild-)thinking about combining Tim Larson's
>> EffectTransformer (http://wiki.cocoondev.org/Wiki.jsp?page=3DTimLarson)=

>> with interpreted code to make it easier to write scriptable =
transforms
>> but it's just a wild dream at this point.
>
> Intriguing idea.  Let me know if you make any progress on this (ideas=20=

> or
> code).  I have no time to experiment with it right now, but this looks
> like an interesting direction.  Eventually the EffectTransformer will=20=

> be
> used for other structured data besides XML, and this scripting idea =
may
> be just the ticket.

The basic idea (again, not tested at all) would be to have your=20
EffectTransformer call pieces of scriptable code, instead of inner=20
classes (IIRC) to handle the various elements. This should be doable=20
using the BSF (Bean Scripting Framework) which is present in the bsf=20
block.

I also have no time to look at this now, but it might be worth trying.

-Bertrand


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