> > Hi all, > > Finally I will be getting around to build a proof of concept, for a > project I will be working on, in pylons. So after all those mails from > me with: "I don't know pylons, just python", this might be a real > change ;) > > I have started looking into what I will really need for the project, > and as it will include quite a bit of forms, I looked into the > FormBuilding stuff. I stumbled upon that sentence: > >> Looking forward it is likely Pylons will soon be able to use the >> TurboGears widgets system which will probably become the recommended way >> to build forms in Pylons. > > The question is: What would be the best practice for building quite a > bit of forms? Is there another way than FormBuild which is already > stable enough for a production site (or will be stable enough in ~2 > months)? Or should I stick to the FormBuild things?
I'm using tw.forms (aka: ToscaWidgets, disclaimer: I wrote a great part of it) in several production sites sucesfully. However, it's got a deserved reputation of being badly documented around here since it stood undocumented for over a year. Anyway, this has recently changed. Better take a walk around http://toscawidgtes.org and judge for yourself :) Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
