Just a couple of comments.
After typing: TableForm(fields=fields(), ids=True) I decided that the all or nothing might approach might not be fine grained enough. Typically, it is only one little element that I need to tweak in a whole TableForm that causes me grief, and a few hours trying to avoid uglifying my code with a hack I don't like. When widgets were introduced, I remember some discussion about how by the time you implement them to be flexible enough... you've just reimplemented the (X)HTML spec in Python. It's will always be a tradeoff, I guess. The other comment is that I suspect that the reason that I sometimes think Rails is more straightforward is that it is a year older. TG has the solid framework in place, but is still evolving in the area of convenience methods. One suspects that more RemoteXxxx widgets (or RemoteToscaWidgets!) will continue popping up where there is an 'itch' to be scratched. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
