deform looks cool. Regarding form libraries: I think approaches like tw.forms are indeed much too magically, if you want to generate just a few forms.
However, if you are building a CRUD application, these libraries provide the necessary abstractions. By the way, of course CRUD applications can (if properly implemented) handle objects spread over several tables (just use SA for mapping them to one object and be careful about deleting these objects). Of course you would not do that for "just a simple form". Cheers, Michael On 20 Apr., 23:00, Ben Bangert <[email protected]> wrote: > On Apr 20, 2010, at 2:45 AM, Martin Stein wrote: > > > 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 > > Chris McDonough has remedied my FormEncode complaints by making Yet Another > Form Library. :)http://docs.repoze.org/deform/ > > It's still a bit early yet in its life, but its 100% unit tested, and has > extensive documentation, which is awesome. > > > 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. > > Not sure if Chris has gotten i18n into Deform yet, I know he's working on it > though if its not in there already. > > > 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. > > Yea, i18n is a tricky thing. > > Cheers, > Ben > > -- > 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 > athttp://groups.google.com/group/pylons-discuss?hl=en. -- 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.
