"Chris" <[EMAIL PROTECTED]> writes: > note: I know 42 fields is a lot of fields, however many of those > fields are "groups" of data that the user will leave as the > default...it's really not as bad as it sounds.
I have a custom widget that has, just by itself, 49 fields... It's not uncommon when you stop to think and to make the interface look like what you have on paper or some other GUI. This particular form has 51 fields + the 49 fields widget + some hidden fields totalizing more than 110 fields. I couldn't do it differently since I can't break the information in two pieces and I have to have it all filled (there are default values, of course!) as a law requirement. > I did toy with the idea that some form handlers with few variables > should be named arguments. I just don't know that I want to tie my > current functions to the current forms quite that tightly. Are form > handling functions really "normal" functions or should we consider them > something slightly different? I differentiate them. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
