GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
For instance, see #217. It occurred to me that if “Mounted Disks” was just an object instead of a proxy object, you could get to the children with a single right-arrow. For an example, see the AirPort object added to the catalog by that plug-in.
It generates children on-the-fly only when arrowed into. Another example can be found in the unreleased Safari plug-in (Open Web Pages).
I’m not sure what to call these types of objects. Proxy object seems appropriate, but they aren’t literally proxy objects from Quicksilver’s point of view. Some people might not like the idea of mixing these in with all the regular objects. I’m not opposed to somehow identifying them as special in the catalog prefs (maybe redefining the proxy objects category to include things of this type), but none of that is necessary to actually implement these things.
So, in other words, Mounted Disks (and probably a few others) should be redefined not to be proxy objects.
You're right... I can't see any use in having "Mounted Disks" being a proxy.
Suggestions from the top of my head :
(BTW, while I'm not directly working on QS atm, I keep my IRC open anyway since I'm on WebDev frenzy).
Here are the ones we need to change: