On Fri, Oct 23, 2009 at 3:58 PM, Kevin J. Smith <[email protected]> wrote: > Thanks for the clarification, Mike. So it is really an issue with the > decorator rather than FormEncode as a whole, correct? As I mentioned, I > have never ran into issues with FormEncode but I have only just started > using Pylons therefore haven't ran across a huge number of cases with the > decorator.
FormEncode's main problem is it needs a better manual, which I'm working on. The examples in the manual are geared toward interactive usage, which leaves you somewhat at a loss for how to use them in Pylons. Which options to use for a checkbox, advanced uses, schemas, chained validators, how the messages work -- these are all things I had to puzzle through at various occasions. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
