Hi Jorge,
On 08 Dec 2005 23:08:56 -0200, Jorge Godoy <[EMAIL PROTECTED]> wrote: > My idea is to provide a form with the common part, where the client can say > what are the processes these samples should be submitted to and then say how > many samples he'll be sending. Something like: > > ================================================================================ > Date: __ / __ / ____ > Process type: ______________ > Process: ____________ > Amount of samples: _X_ (lets say here he inputs 5) > > ID Weight Type > S1) _____ _______ _______ > S2) _____ _______ _______ > S3) _____ _______ _______ > S4) _____ _______ _______ > S5) _____ _______ _______ > ================================================================================ > > Lines from "S1" to "S5" contains input fields, selects, checkboxes, etc. and > there should be "X" lines, where X is the value the client informed (if X == > 6, then there would be a line "S6"). What do you think of the "add row/remove row" model? It should be possible, to make a container widget that knows what kind of entry widgets to use for each row, use JavaScript to add/remove those as needed, and to use FormEncode's variabledecode capability to automatically get a nice set of data back. The one thing that's missing is ability to change the widget's name for each rendering (but we can come up with an API to do that). Kevin
