FormAlchemy and formencode are two things. Have a look at FormAlchemy, it's quite nice, it has a set of default widgets while you can extend it. It's originally mapped to SQLAlchemy objects, but now works for CouchDB schemas, Zope.schema, and some others. It even has a Pylons automatic admin interface.
Coming from Django, I guess it's your best bet. Alexandre Le 20 avr. 2010, 5:45 AM, "Martin Stein" <[email protected]> a écrit : For me, the main reasons why I like Django's forms are: a) html widgets (without having to maintain my own mako form widgets library, as in Mike's approach) b) I mostly understand the source code c) well documented Also, I've never really felt comfortable with formencode. I can't really explain it any better than what you've written here: http://groups.google.com/group/pylons-devel/msg/cab1ce37e61d7b96 I didn't want to question Pylons' commitment to formencode... sorry, if my original message came off that way. I'm sure that for many people formencode/ToscaWidgets or Mike's approach work fine. This is more of a personal preference towards WTForms or Django forms. Unfortunately, WTForms still lacks i18n completely. Thus my attempt at extracting Django's forms. I've never written a (distributable) python library before, but that is very well explained here (http://guide.python-distribute.org/). What I'm still missing is the translation/i18n part. Formencode allows several different ways (http://formencode.org/ Validator.html#localization-of-error-messages-i18n), Django uses another approach... and I'm somewhat lost now how to proceed. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" grou... -- 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.
