One thing that turned me against ToscaWidgets and other widget generators (FormAlchemy) is that there's essentially a mini-template somewhere generating the HTML, plus other templates for each widget type. So customizing the HTML means overriding those templates, which are in a different location and maybe in a different language than your page templates. That made me feel like "What's the point?" when Mako has such powerful function tools to make the layout just the way you need it.
I'm still interested in ToscaWidgets for the widget-HTML-Javascript bundling... after the C dependencies and injection issues are resolved. So I think Pylons was right to offer a minimal approach as a baseline, and then support other approaches as extras. And I'm glad that FormEncode/htmlfill is so modular that it can work with all these approaches. -- 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 pylons-devel@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
