Comments on: Quicksilver plugins in Objective-C

By: Charlie

Charlie — Sun, 27 Jul 2008 17:11:37 +0000

Thanks to Anonymous for helping point out that the Leopard (or rather Xcode 3.1+) path for Bundles has changed — but I don’t have a Developer folder under App Support, it’s only under App Support/Apple/Developer Tools. If I manually create this directory hierarchy it’s ignored by Xcode. Any ideas what the path should be in Leopard (Xcode 3.1) i /Library/Application Support/Developer/Shared/Xcode/Project Templates/Bundle/Quicksilver Plug-in isn’t working for me?

By: Devo « chimney

Devo « chimney — Wed, 16 Jul 2008 16:33:33 +0000

[…] a launcher for which the barriers of entry to creating new actions are low. Quicksilver actions are tough to write for someone who doesn’t code in Objective C but on the other hand, everyone knows a modicum of […]

By: Anonymous

Anonymous — Tue, 03 Jun 2008 22:19:12 +0000

/Library/Application Support/Developer/Shared/Xcode/Project Templates/Bundle/Quicksilver Plug-in

is the correct path for Leopard, btw.

By: Quicksilver updated! › Vacuous Virtuoso

Quicksilver updated! › Vacuous Virtuoso — Mon, 20 Aug 2007 05:15:47 +0000

[…] you’re developing plugins for Quicksilver and running Leopard, you may want to download this new release. Gregarious […]

By: Write your own Quicksilver interface › Vacuous Virtuoso

Write your own Quicksilver interface › Vacuous Virtuoso — Wed, 13 Jun 2007 09:55:26 +0000

[…] Writing an interface is very similar to writing an action, but the classes and Info.plist keys are somewhat different. Download the QS Interface Project Template. If you haven't previously downloaded a Quicksilver plugin template for Xcode, you'll have to do some basic setup. […]

By: iPhones4U.info » Blog Archive » Roll Your Own Quicksilver Plugin

iPhones4U.info » Blog Archive » Roll Your Own Quicksilver Plugin — Mon, 21 May 2007 00:10:00 +0000

[…] a Quicksilver plugin with Xcode in Objective-C. So far, only the first two parts are available (an Introduction, and an Anatomy of a plugin), but three more parts are planned. So all you developers out there […]

By: Ankur

Ankur — Tue, 17 Apr 2007 22:45:55 +0000

Sorry Calvin, adding it in now.

I did have

You wont find a QSActions key in the Info.plist file. It’s named to QSActionsTemplate by default. This is to stop Quicksilver parsing the default data which is automatically added by creating a new project.

But I guess that's too ambiguous.

The QSPlugIn key doesn't start off as "QSPlugInTemplate", but most of the registration keys are appended with "Template".

All fixed!

By: Calvin

Calvin — Tue, 17 Apr 2007 19:16:03 +0000

Taking a further look at the two tutorials, Ankur you need to be clearer in telling people that the Templates are just that - Templates. Renaming them to the actual items required by QS does a world of good in getting a working plugin.

Calvin.

By: Calvin

Calvin — Tue, 17 Apr 2007 18:35:07 +0000

Has anyone actually managed to create a working plugin using this tutorial? I've tried over and over again but it never works. This one does work though. Info.plist is vastly different and code changes are different but it worked 1st time.

Any comments Ankur?

By the way I'm on Tiger (10.4.9) using XCode 2.4.1 and with latest QS release (development)

Calvin.

By: Ankur

Ankur — Wed, 04 Apr 2007 23:51:30 +0000

Sorry Colin, I will post up another few articles sometime soon, but creating interfaces and such requires quite a bit of explanation and planning.

If you've gone through the Info.plist setup and played around with writing actions for Quicksilver, you should be able to create any sort of action using regular Obj-C code.

Anyway, please do continue to post feedback, criticism and the like. It really helps. That next article is coming.