Stephen Compall <[EMAIL PROTECTED]> writes: > Jan Rychter <[EMAIL PROTECTED]> writes: >> There can be multiple dispatchers in a widget tree and not all >> arrangements of dispatchers and selectors will make sense. Also, usually >> dispatchers will want to dispatch on a fixed number of URI tokens, but >> that is not enforced. > > It doesn't sound like a dispatcher is a widget at all. If a dispatcher > does not render, how can it be a widget, and how can it be in the widget > tree?
This is a good question. I wondered about that, and I believe the only reason for the dispatcher to be in the tree is to have hierarchical navigation systems, where the order of consuming uri-tokens is determined by position within the hierarchy. Instead of having a global dispatch table you basically delegate dispatching knowledge down the tree. I am not entirely convinced this is the best approach -- but it is the approach weblocks traditionally took. Django, for example, has an entirely different take on it. I figured people would want to keep the current approach, and as I don't have strong arguments either way, left it that way. I don't think rendering has much to do with it, though -- we have other widgets that do not render (containers?), but serve useful purposes within the tree. --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 -~----------~----~----~----~------~----~------~--~---
