Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 63907 invoked from network); 3 Nov 2003 10:02:54 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Nov 2003 10:02:54 -0000 Received: (qmail 26278 invoked by uid 500); 3 Nov 2003 10:02:20 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 26250 invoked by uid 500); 3 Nov 2003 10:02:19 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 26225 invoked from network); 3 Nov 2003 10:02:19 -0000 Received: from unknown (HELO kerberos) (62.116.51.59) by daedalus.apache.org with SMTP; 3 Nov 2003 10:02:19 -0000 Received: From mail.at.efp.cc ([62.116.51.60]) by kerberos (WebShield SMTP v4.5 MR1a); id 106785375019; Mon, 3 Nov 2003 11:02:30 +0100 Received: from WRPO (wrpo.at.intra.efp.cc [194.107.80.148]) by mail.at.efp.cc (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id hA3A2NM01108 for ; Mon, 3 Nov 2003 11:02:24 +0100 From: "Reinhard Poetz" To: Subject: RE: Dynamic woody templates? Date: Mon, 3 Nov 2003 11:01:52 +0100 Message-ID: <001f01c3a1f1$82085400$1e01a8c0@WRPO> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N From: Sylvain Wallez > But I'm also wondering, as woody usage increases, if we will > not need to > write form templates involving more and more conditional > parts. And for > this, JXTemplate shines. But mixing jx-like access to the form model > with wt: templates elements is likely to quickly become unnatural. A > solution could be to augment the JXTemplate syntax with new > Woody-related instructions. Taglibs for JXTemplate? > > What do you think (again)? I think what we need is a possibility to extand a basic JXTemplateGenerator/Transformer to add your own syntax. Otherwise we will end in many different *TemplateGenerators/Transformers which have to be maintained separatly. But I think you meant this with Taglibs, don't you? Anyway, a big +1 for *one* official *extensible* templating approach in Cocoon - otherwise we will confuse our users. -- Reinhard