On Mon, Feb 16, 2009 at 4:57 PM, Ian Eslick <[email protected]> wrote: > Perhaps a variation of this mechanism could also be used for long- > distance widget lookups. I agree that it's necessary to have one. A simple index by widget id would suffice, I think. Looking up widgets by path in the tree never worked for me because I can never easily figure out what the path is.
On Mon, Feb 16, 2009 at 5:09 PM, Jan Rychter <[email protected]> wrote: > Please remember that we also want these children to be ready to > participate in flows, so storing them in different ways isn't a good > idea unless one wants to write multiple make-widget-place-writer > functions. In particular, I found that storing widgets in slots and > ad-hoc lists really isn't such a great idea. I agree, I think there should be one uniform way of doing this. I think what I proposed fills this requirement (of course proposing something and coding it are two different beasts :]). > Also, an append method combination fixes the ordering, which in my case > is a no-no. Ok. I think this is easy to fix, though. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
