> Interesting idea, and I think I like it, with one small qualm - isn't > it already the job of a view to act as a renderer, and wouldn't > creating another option for rendering (on top of the options available > of implementing render-object-view-impl for a new view or just > subclassing dataform and rewriting render-widget-body) be a bit > redundant? It's already unclear to me who should be responsible for > rendering what - the view or the widget?
Ah yes. I picked the wrong part as target for the custom renderers. *Form view* should in fact be parameterized this way, not the dataform widget. > Additionally, do you see renderers being something used only for the > dataform widget or something that might be used across other widgets > as well? They mostly only make sense to me in the context of > dataforms, but just curious about what your thoughts are. I think form views take a special place here because you cannot bypass them easily by writing your own widgets. Table views pretty much have only one way of being rendered, and data views are most of the time quite useless except when prototyping. So like your event handler feature it's probably best to concentrate on the form view part first and maybe later extend it to other components. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
