"Adam Jones" <[EMAIL PROTECTED]> writes: > I tried that earlier, didn't get terribly far due to being really >tired. Unless I am seriously missing something the TableForm idea won't work >as it hardcodes its own form tag (and associated name/action/method attrs) >and submit button. If you were suggesting that multiple parts of a single >form be split up, that also does not work with a TableForm as it expects a >label attribute for each field, and would practically implode when trying to >convey form errors.
It gets messy... But we might come up with something that works... > While I was at it I wrote up something for that, as it seems to pop up > on the list pretty often. I'd like to work on this and make it a good > set of tabber-related code. You can get an svn co here: > > https://recursivethought.googlecode.com/svn/tabber/trunk It asks for user/password. :-( >> Anyone needing something more elaborated than that and willing me to take a >> look at it for a new widget? > > I can think of a few: > > * A tabber widget that loads each tab through AJAX instead of during > the page request. > * A paginate-aware tabber, possibly based on the above. Those might be extensions later. I plan on starting with the basics. ;-) > Both of these probably belong in the "that would be nice" pile, if not > the "lets dream up something that sounds cool and is impossible to > implement" pile. :-) -- 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?hl=en -~----------~----~----~----~------~----~------~--~---
