Poll for readers: do *you* understand the difference between children and subwidgets as explained in http://groups.google.com/group/weblocks/msg/dea98b024b164c40 ?
Jan Rychter <[email protected]> writes: > As to navigation-rewrite branch (not sure if that is what you meant), > this is still a work in progress. Yes, weblocks-nav4 on Bitbucket is just cherries (with aforementioned fixes) of your navigation-rewrite branch. > Today I managed to rip out container and composite altogether, along > with all their supporting machinery. Turns out they were just artificial > constructs, complicating things. The only cost is an extra slot in > widget and a change in the rendering protocol (I introduced an extra > render-widget-children GF). There is also the danger that it will be even harder to explain the difference between the two notions of children/subwidgets (the latter being the superset) then it already is. > cleanly implement tree walking, based on your suggestions. I now think this should be based on: (defgeneric map-subwidgets (proc wij) (:method-combination progn) (:documentation "Call PROC on each [direct] subwidget of WIJ.")) as the only real problem with walk-widgets as a GF is it forces full descent in a particular order, which map-subwidgets doesn't share. DFS and BFS and whatever else you like can be implemented on top of this. -- Sorry but you say Nibiru is a Hoax? Doesnt Exist? So maybe The Sumerian people doesnt exist also! --Anonymous by way of SkI --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
