> From: Marc Portier [mailto:[EMAIL PROTECTED] > Sent: Monday, December 22, 2003 12:07 PM > To: [EMAIL PROTECTED] > 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
