Hi Max, Michele is right, you should try using the disabled fields param. To display those fields in another table you could add them to a different category in the widgets dict:
widget.widgets['fields2'] = whatever And taking care at update data of fetching them for the template. Just make sure the name of these doesn't collide with fields at other categories. The new validation implementation (SVN) assumes child widgets will be fixed at __init__ time, that is, no more fields will be added or any field will be removed once the widget instance comes into life. This is really needed because it's way too complicated to validate a nested form otherwise (a new schema will need to be generated at every validation which is a waste of resources) and there will be no way to know at validation time which fields where displayed at display time so it knows which fields to expect (to filter spurious input). You can take a look at the validation at .9a1 and SVN to notice the *big* difference :) Regards, Alberto On 13/03/2006, at 11:32, Max Ischenko wrote: > >> You can use only one form and then the disabled_fields parameter, I > guess it should work but I haven't actually tested it. > > I'll look into it, thanks. > > The problem is that I need to display those extra fields differently, > e.g. in another (separate) table from the main list of fields. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
