Alberto Valverde wrote: > You can store the template in a separate file just to ease this use > case:
Maybe *I* can, but none of the widgets in the tg install have bothered. > 1) Encapsulate most of the view logic for common patterns into a > python egg for easier redistribution, along with all required > resources like css and js files which get automatically pulled into > the template a widget is placed into. Take a look at the Plotkit, > TurboTinyMCE, SelectShuttle... widgets for examples of this. This would be great, if I could ever use these things without having to edit the accompanying css/js files, which seldom seems to be the case. > 2) Handle form validation in quite a powerful and flexible way > through FormEncode: Form widgets automatically generate a schema to > validate the input generated by all the widgets contained in it, also > handling the input-name mangling to support nested structures > (fieldsets) and lists (repeating fieldsets). This could be cool; I stopped experimenting with the automagic form creation stuff once I realized that adding sufficent accessability components meant overriding the templates/controllers to the point that I might as well just, well, write an html form ;) Sufficient in this case means: proper <legend> grouping, <labels> that work no matter where the form is embedded (a corner case for me, I'm aware), longdesc attributes that get fetched for sighted readers via XMLHttpRequest, accesskeys where appropriate with some display of what accesskeys do what, control over where and how error messages are displayed, etc. With the spiffy tabular widget, there are a bunch of other accessability issues, but I'm too strung out to go into all of them at the moment. Basically, if you're willing to live with all the assumptions that the widget-writer made, you can use widgets ok; I just feel like (at the moment) it's way too difficult to change those assumptions you need to change for your app without digging through half a dozen layers of indirection. ~ethan fremen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
