Jan Rychter <[EMAIL PROTECTED]> writes: > 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.
Containers do render; you are required to come up with a render for them. If, and I believe it is sensible to keep this setup, a dispatcher must be hierarchically positioned above sub-dispatchers, then they cannot be pure leafs. Since this is the case, each dispatcher must accept at least one child, and this might as well be the function-selected cache. The idea of a dispatcher choosing widgets elsewhere in the tree is certainly valuable. But this can happen anyway; it is merely a matter of communication. For example, a dispatcher that you do not wish to select for different widgets at that point in the tree, but at some other arbitrary points, can adjust those locations manually, and always return the same widget to be "selected". This permits the sophisticated tree-disconnected-selection that we would like, without undue complication of the simple case of a standalone ephemeral-selecting dispatcher that is suitable for many cases. It could not be done with the dev dispatcher (because the widget you might like to select differently might already be rendered), but can be done with the two-stage style. -- 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 -~----------~----~----~----~------~----~------~--~---
