I've switched to using django.forms with Pylons, and I really like the change so far. I've posted a writeup, and a drop-in module, on using django.forms with Pylons here:
http://marcuscavanaugh.com/posts/pylons-django-forms/ Also, if django.forms isn't your thing but you still want to use FormEncode, I included some code that lets you use FormEncode validation with django-style controller code (to replace @validate). I've thought about @validate for a long time now, and I don't think a decorator will ever give the flexibility we need; Django's idioms work equally well for FormEncode, so maybe that will spark your interest. YMMV, of course, but I'm using Django's Forms with my project now and I'm very happy with it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
