Perhaps a variation of this mechanism could also be used for long- distance widget lookups. For example if I want to link from one currently viewed widget to another one that is currently down a different select branch.
I might need to do this if that widget has exposed parameter state, I need to ask it for its current parameter list. Ian On Feb 16, 2009, at 4:53 PM, Vyacheslav Akhmechet wrote: > > Actually, since people mostly keep child widgets in slots because they > need to access them individually, it would be cool to provide a > hashmap/association list interface so that one could get and set child > widgets in a widget by name: > > (setf (child-widget parent-widget 'child-name) child-widget) > (child-widget parent-widget 'child-name) > > And of course one could implement (child-widgets parent-widget). > > This association can be stored in a per-session hashmap, not widget > slots, so it would avoid the multiple inheritance issue. The benefit > is that one could easily store and access child widgets as one does > with slots, which is immensely useful, without having to use an > additional interface to specify the child widgets for weblocks > machinery. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
