On Aug 25, 11:05 pm, Stephen Compall <[email protected]> wrote: > The presence of render-widget-children (on-demand-selector) and > (navigation) implies, to me, that if you want a class to render children > not associated with :widget, you should implement an RWC method > yourself. > > If I understand Jan's design correctly, RWC (widget) only selects > :widget-associated children for rendering to give subclasses of widget > control over _when_ and _if_ children are rendered. Whether this is > worthwhile, or those interested in such things should use subwidgets > instead, I leave to that long slot-vs-GF thread we had when we were > figuring all this out.
I'm not sure about the original design motivation, so I'm going to leave it as it is now (i.e. there's the need to specialize RWC if you have widgets you *don't* want to render). Discussion and patches welcome, of course. Leslie --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
