On Jan 13, 5:09 am, Jan Rychter <[email protected]> wrote: > the interface somewhat nicer -- but I'd still want to keep the > {get|set}-children-of-type methods, because I have widgets that maintain > two or three lists of children. As an example, a "commentable" mixin > widget maintains a comment bar with a comment count and an action link > and a pageable list of comments. The comment bar is on a > :commentable-comment-bar list -- so that it can be replaced by an editor > when a "comment this" action is initiated. That's just immensely > useful. Same for rendering, it is much easier to lay things out without > having a big bag of all children all mixed up.
This description makes get/set-children-of-type sound like a harder-to- use solution to the same problem that map-subwidgets solves. Does it solve any problems other than child/subwidget list composition? -- You know... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
