I've been trying to reverse engineer widgets/forms.py for about 7 hours now , using the wiki samples as a starting point . i kind of expected having something up and running
your sample is a godsend for this alone: email = TextField(validator=Email(not_empty=True)) i've been going crazy tyring to set up a way to do a chained_validator on Email . i never saw taht option in validators.py or FormEncode. i think i'm going to try and make an abstracted form class though - i'm really partial to the approach of having a class that calls all the widgets (if thats what you want ) or the access the args ( if thats what you want ) and can create an appropriate output ( perhaps for tal instead of kid ). aside from being able to switch outputs at the user level, an approach like that *should* be able to help compensate for API changes ( like how the .8x doesn't work with .9x etc ) anyways, thanks a ton for that explanation - you should add that to the wiki. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
