well I've seen widgets change slightly througout the .9 releases - i know its alpha, but things seem to fluctuate far too much for my tastes
I understand the FormFieldsContainer compound widget - but to me, it shows how awkward some form stuff is in TG. You end up with a few defs and classes for one form. i want to consolidate things into a class that a ) has all of the form fields info, b ) has all of the validation info , and c ) lets me either handle the form creation/validation through widgets , or through a widgetless form that uses the same FormEncode validators. It would handle all the FormFieldContainer and widgets etc behind the scenes. As a developer, I'd just interface with a single class that does pretty much everything for me -- either widget or widgetless. If anything odd happens in the API in regards to restructuring or name changes, the base form class classes are derived from will update to keep everything else frontwards compatible. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
