On Jul 2, 2012, at 8:53 AM, Rob McBroom wrote: > On Jun 30, 2012, at 1:15 PM, su wrote: > >>> * Have a 'Proxy object' called 'All Menu Bar Items' or similar, but this >>> would require you to → into the proxy object to obtain the list (could be >>> slow, as you mention) then search for your specific menu item. >> >> Why not a trigger with (to be implemented) 'All Menu Bar Items' proxy object >> ⇥ Show Menu Items? You could then start typing right away without messing >> with other catalogue items. > > OK, but it shouldn’t be a proxy object. There’s been enough abuse of that > already. :-) > > https://github.com/quicksilver/Quicksilver/issues/654 > > We should come up with a name for objects that serve no purpose other than to > be the parent to other objects.
Collection Objects? I see the distinction, I'm not sure it needs to be exposed to the user. (These are just like proxy objects but are slightly faster and don't need an extra button press). Howard -- You received this message because you are subscribed to the Google Groups Quicksilver 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 https://groups.google.com/d/forum/blacktree-quicksilver?hl=en
