On 14/03/2006, at 14:23, Jorge Godoy wrote: > Wrong... I have more than 10 forms on the same page. And this > will also be > common with the TabWidget where everything is on the same page and > "beautified" to be in tabs...
Jorge is making some good points here... Maybe we should support multiple forms per page (arggg). The hack at the schema generation is already done and works so don't need to worry about it... Dunno exactly the problems you're facing at display_field_for exactly but maybe could be solved somehow... could try to help if you tell me exactly what you want to do. I know I'm contradicting my prev. post, but it's true that people might want multiple forms... :( I think we need more feedback on this... Attention people, RFC: Would you want the Form widgets to support multiple forms per page? Your controllers will need to receive the whole form as input like def controllermethod(self, form): If you want to receive data from a FQF. It will be a (possibly) nested dicts representing your form's struucture. Normal paramters for non-FQFs. This cannot be easily solved so don't come complaining later... :) > I agree that too many hacks are wrong... :-) Maybe we can change > those to > "technical implementations" :-) (Just kidding) Patches are always welcomed :) Alberto --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk -~----------~----~----~----~------~----~------~--~---
