Jan Rychter <[email protected]> writes: > In particular, if you think about how the current navigation works, you > realize that it has serious limitations -- for example, it uses dynamic > variables
This is a manifestation of using CUC and CUDC. Eliminating these solves the problem, by letting you pass a closure to WALK-WIDGETS or something instead of just plonking a hodgepodge of methods onto a GF and hoping the others cooperate. > You can't have one part of the tree affect another, and then > place a selector in that second branch that reacts to subsequent url > tokens. That is a problem for example if you want flexible navigation > with detachable menus, which is what I need. Any solution that would remove the depth-first limitation would also make a new tree and either ignore or overcomplicate flows, so given the philosophy of "URL as entry-point", I think to solve this you should just add another phase that is just a function someone can plug in to tweak the widget tree right. Maybe this phase already exists. Even now we can slightly alter this; BFS is almost as easy to implement on top of whatever generate-subwidgets becomes as DFS. -- I write stuff at http://failex.blogspot.com/ now. But the post formatter and themes are terrible for sharing code, the primary content, so it might go away sooner or later. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
