From: Hancock, D. \(DHANCOCK\) <DHA...@ar...> - 2005-05-25 16:19:19
|
First, thanks for all the assistance so far with ZPTKit and FEComponent and FormEncode. We're getting close to understanding things. A developer in our group (not a list member) asked me to post the following questions: The FormEncode documentation and the FEComponent frequently state that we can call validators.to_python, which apparently returns a requestDict that we are in dire need of. After looking at all the source, we noticed that validators.py doesn't have a to_python method but instead has a _to_python() for each validator that inherits from FancyValidator. We tried using the to_python() in the api.py->FancyValidator class but the arguments are different. For example: =20 The to_validator in api.py, FancyValidator.py, etc are all defined as: =20 def to_validator(value, state): =20 The FEComponent.fecomponent.py tries to make a call to validators.to_python(NestedVariables, rawFields), which doesn't exist. The other problem is that NestedVariables is a class in variabledecode.py that is derived from api.FancyValidator() so the to_python here is doing something much different. I guess what I'm trying to say is that this was doing some magic we are unable to reproduce. =20 Do you know if we can find an older version of FormEncode or better yet, point us in a direction where we can see what the above to_python is really doing? =20 One thing to note is that we had to make changes right out of the box to get FormEnocode working since htmlform.py was trying to import something from validator and not validators. Thanks, and Cheers! -- David Hancock | dha...@ar... | 410-266-4384=20 |