How hard is it to define a URL protocol that invokes Quicksilver with a string already loaded?
Could you make a URL protocol, call it qstp, where "qstp://this is a string" invokes quicksilver with "this is a string" in the first field? Then I could supply a greasemonkey script or FF plugin that captures the selection when you hit command-escape, and then redirects you to the url at qst://your_selection_here. It'd also be nice to have a quicksilver object protocol, like qsop://Path/to/file, that does the same thing for files. I can imagine plenty of uses for both protocols. Unfortunately I can't find the source for the web search plugin to see how Alcor quicksilver implemented the qss protocol. Is that source available? On Aug 31, 1:01 pm, Howard Melman <[EMAIL PROTECTED]> wrote: > Your trick using the Clipboard Contents proxy object is a good one. It > does indeed require the Clipboard plug-in and it does seem to work in > B4 on Leopard even with it's proxy object problems. Creating other > triggers using the Clipboard Contents proxy object and other actions > (like web searches or dictionary lookup, etc.) should work too. > > Also, the simple way is to use cmd-v right after activating > Quicksilver (control-space) to paste the clipboard into the first > pane. That's just one keystroke more. > > Howard > > On Aug 31, 2008, at 12:31 PM, Benton G wrote: > > > > > A kind of clugy workaround that I sometimes use is to enable the > > Clipboard plugin and set up a trigger to bring up the clipboard > > contents (useful even if you don't use it for this workaround). Then, > > whenever you want to do something to text in Word or Firefox, or some > > such application, you select it, hit Cmd-C, hit whatever your hotkey > > is for the clipboard contents in QS, and now you can work as if you > > had just invoked QS with the selected text. Granted, that's one extra > > key command, but it does work... > > > On Aug 31, 9:30 am, mason k <[EMAIL PROTECTED]> wrote: > >> Just to riff on what Melman said, "Cocoa" is mainly a library (API) > >> that offers a bunch of interface elements to programmers. MS word > >> doesn't use cocoa because it's a fake Mac port (and nothing MS > >> touches > >> is right). Firefox doesn't use cocoa because their cross platform > >> plugin architecture is heavily reliant on the interface API that they > >> do use, which is called XUL. As long as Firefox offers the > >> extensibility that makes it Firefox, it won't be written with Cocoa. > >> I actually switched to Safari because of this problem, but I do miss > >> Firefox - a lot. Especially since FF3 is so snappy compared to > >> Safari. > > >> I bet someone could hack up a workaround to this problem using a > >> firefox plugin... > > >> On Aug 28, 8:54 pm, Howard Melman <[EMAIL PROTECTED]> wrote: > > >>> Getting the selection from another application is difficult. An > >>> operating system, in part is supposed to keep apps from interacting. > >>> QS's method works with applications that use the cocoa framework. > >>> Those apps that don't, don't work. If the apps start using cocoa > >>> (and > >>> probably something specific within cocoa) they should work. > > >>> Howard > > >>> On Aug 28, 2008, at 7:38 PM, RC wrote: > > >>>> I've read that QS does not support these applications in regards to > >>>> Queing up QS with selected text? are there any solutions what so > >>>> ever? Mozillas new ubiquitous does it well, a mix between the two > >>>> would be wonderful.
