I finally started making forms in my app this week. I found Mako more convenient than any of the form libraries. I use a call-with-content to format an input control with its title, hint, and error message. Then htmlfill to set both the initial values and the error messages.
ToscaWidgets has too many dependencies; it almost doubles the size of Pylons. Plus I understand the TW team wants to get rid of a couple of those dependencies, which Pylons has already jettisoned. lxml is required for TW's Javascript features. FormAlchemy was not flexible enough for my needs, while DBSprockets has lots of dependencies that's overkill for it. Somehow while testing all this I ended up with Genshi installed; I'm not sure what depended on it. Most of the HTML webhelpers were so trivial I didn't see much advantage over writing the HTML by hand. options_for_select was the only one I ended up using. Using static HTML has the advantage that my colleague can preview the template in a browser and adjust the layout & style. So I'm almost wondering if we should drop a lot of the HTML helpers rather than upgrade them. On the other hand, I guess basic tag functions are useful when you're generating the attributes dynamically. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
