Nando, >I have written up the above page about why I was unsatisfied with the >interface of TG widgets (which puts widgets in our controllers instead >of our template) and why I am making a new interface: Formetto. > > It's great to see a different approach to widgets.
There is definitely a need for some kind of reusable components, and a forms library. In the Python world, TG widgets were probably the first credible system for this (does anyone know anything earlier?) The dependence on the controller is a niggle, and I hope an approach like yours can be incorporated into ToscaWidgets. For most of my apps I will continue to define widgets in the controller, primarily generating them from the model (using fieldfactory). But if I find a form where I need particularly granular control of the HTML, this would be fab. I've realised, widgets have to work extremely hard to include the js/css links, quite disproportional to the benefits of this. I wonder, is it enough to just include each link right next to the first widget that needs it? That could be implemented much more easily. Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
