Vyacheslav Akhmechet <[email protected]> writes: > 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.
Here's something I really would like to understand: could you please describe a use case where you have to find a widget in the tree? The reason I ask is because in all of my code whenever I need to link between widgets, there is always a place in the code where the linked widgets are processed (or created) together, so one can simply store a reference to another and there is no need for walking the tree to find anything. In general, weblocks has a mutable approach to data, so we can safely keep references without them becoming stale. In a purely functional language you would need to find widgets by name or path, but not necessarily with Weblocks. Since this is a design decision, let's use it to our advantage. --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 -~----------~----~----~----~------~----~------~--~---
