On Fri, 2002-02-01 at 16:11, Luke Opperman wrote: > Hi there - > > We have an existing (non-webware) system that reads a bunch > of meta-data about one of several database tables, and > generates a dynamic form based on the fields in the table > and the meta-data. > > I'd like to convert this to Webware, but I'm running into > issues using FFK because it seems to require that the form > fields be known at __init__. > > Any thoughts?
In what ways are the form fields varying? There's things in their for dynamic select fields, and you can hide fields, which provides a certain dynamicism -- you can define a form with all possible fields, and hide the ones that aren't necessary. The reason it is defined in __init__ is because the form generation/validation/regeneration process always has to be working off the same form definition -- if the definition is dynamic, you might be validation based on a definition that doesn't match the definition used to create the form. I did play around with the idea of a MutableFormDefinition -- the code for which is still in Form.py, but still untested. Ian _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
