Stephen Compall <[email protected]> writes: > Jan Rychter <[email protected]> writes: >> We should also probably have a nicely generalized tree walk method for >> those cases when we really lost a widget and need to find it. I already >> have two similar methods like this in my tree: one for containers (a >> modified version of your container-update-children) and another one for >> building breadcrumbs. I kept them separate because I wanted to use >> method dispatch for finding navigation widgets, but one could presumably >> write a generalized tree walking method. > > See `walk-widgets' in my modern-dispatching branch for this. It is a > simple function because the real generic interface is > `generate-subwidgets'; users can safely build all sorts of walking > functions on top of this, such as one with selective-descent features > like Python's os.walk, one with value reduction, and so on.
Stephen, Are you talking about this fork: http://www.bitbucket.org/S11001001/weblocks-modern-dispatching/ ? Where would I find the walk-widgets changeset? I can't seem to find it. Grep -r in the tree comes up empty as well? As to generate-subwidgets, I am not at all convinced that generators are needed. I think they add unnecessary complexity. --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 -~----------~----~----~----~------~----~------~--~---
