Hi Matthew, > I typically define forms explicitly as discrete classes -- and the same > for elements. What I would suggest is that if there are common elements > you use across multiple forms that will be using the same > validators/filters/decorators/etc... then create a custom element:
Yep, that sounds like a very interesting approach to me. Though it might lead to over-engineering the forms if I have to create a lot of custom elements. But that depends on the level I want to separate the dependencies between forms and models. Thanks, I will play around with this for a while. > A single model can certainly have multiple forms -- the example I > displayed was just a simple one. > > Have a getter for each form, or have getForm() accept an argument > indicating the form to retrieve. Yep, I was thinking about this myself this morning before I read your mail. Not really a big deal. Thanks and best regards, Ralf
