Return-Path: 
 <dev-return-53398-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 57177 invoked from network); 22 Dec 2003 12:04:18 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 22 Dec 2003 12:04:18 -0000
Received: (qmail 1407 invoked by uid 500); 22 Dec 2003 12:04:14 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 1386 invoked by uid 500); 22 Dec 2003 12:04:14 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 1373 invoked from network); 22 Dec 2003 12:04:13 -0000
Received: from unknown (HELO smtpzilla2.xs4all.nl) (194.109.127.138)
  by daedalus.apache.org with SMTP; 22 Dec 2003 12:04:13 -0000
Received: from pt (a213-84-18-216.adsl.xs4all.nl [213.84.18.216])
	by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with SMTP id hBMC4CA7071828
	for <dev@cocoon.apache.org>; Mon, 22 Dec 2003 13:04:12 +0100 (CET)
From: "Hugo Burm" <hugob@xs4all.nl>
To: <dev@cocoon.apache.org>
Subject: RE: Selectors for Woody FormManager and BindingManager
Date: Mon, 22 Dec 2003 13:04:51 +0100
Message-ID: <EAEBKKLDONJPPKMHADFFEEIDDPAA.hugob@xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <3FE6D06E.7010105@outerthought.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
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: Marc Portier [mailto:mpo@outerthought.org]
> Sent: Monday, December 22, 2003 12:07 PM
> To: dev@cocoon.apache.org
> Subject: Re: Selectors for Woody FormManager and BindingManager
>
>
> quite a coincidence in fact since I've been exposed to a use case
> recently that also pushes in the direction of having a plugable
> FormManager...
>
> In short: think about a huge apllication-metadata-repository that can be
> consulted online to know what goes on a form (depending on
> user/role/runtime config)...
>
> in these cases it really doesn't make sense to first produce
> (dynamically) the form-definition XML format?
>

Agree. I now must dynamically build the XML form- and binding-model and then
feed it back into a parser, which doesn't make sense.


>
> >
> > Thus the CustomFormManager builds the <wd:> Form definition
> model from the
> > files above, The CustomBindingmanager builds the <wb:> binding
> model. The
> > generator generates SAX events and inserts the cached <wt:> templates.
> >
>
> hm, you might consider using the woody-generator in stead
>
> in fact, as a first step into supporting the above described stuff I'm
> well into attemptig to revive the use of the generator for woody ...
>
> my plan is to separate the current woody-template-transformer from his
> configuration features so that separated class can be used from the
> generator as well
>
> as such I hope that future updates on the possibilities of the
> transformer will more naturally flow back to the generator as well?
>
>
> wdyt?

I was already looking at the generator, because I want to combine inserting
the templates and doing the first tranformation step. So it will be a good
thing if the generator is kept in sync with the transformer.
If you are going to refactor the transformer, have a look at that long
if-then-else statement in <startElement> and <endElement> and think about
what is going to happen when more types of widgets arrive...



Hugo