Jan Rychter <[email protected]> writes: [...] > When you use inheritance you do run into a problem if two widgets wish > to set widget-children. Well, try not to do it then. My pageable-list > mixin usurps widget-children -- you can still have subwidgets in > whatever you derive from it, but you have to be careful. I am not yet > sure how often that will be a real issue in practice. [...]
One more thought on this -- I don't really understand how your solution (Stephen) determines ordering. If you inherit from two widgets both of whom have renderable children, then even if you avoid the widget-children clash, you still have to impose rendering order. How do you do it? A really general solution would do this during the tree shakedown phase: 1) combine all children from all widgets in the inheritance hierarchy, 2) determine the subset of renderable children, 3) specify in what order these are supposed to be rendered (first these children, then those children, etc.) I don't think we have a good way to do (3). --J. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
