Writing an action
Previously
We set up Xcode for Quicksilver plugin development, created a Quicksilver plugin project and got familiar with the QSPlugIn portion of the Info.plist file.
We’ve introduced ourselves to Quicksilver, and told it some fundamental information about the plugin we’re making in the QSPlugIn section of the Info.plist file associated with the Quicksilver project.
In this tutorial, we look at the procedures involved in specifying and writing an action for Quicksilver.
Continue Reading Writing Quicksilver Plugins: Actions
Previously
We discussed the basic setup required to begin writing Quicksilver plugins in Quicksilver plugins in Objective-C. Anatomy of a plugin
is a multi-section guide which explains the various sections of Info.plist, the different components of a plugin and the basic groundwork required in order to write a usable plugin.
To go through this guide, you need to have followed the steps in Quicksilver plugins in Objective-C. Once you’ve got Xcode set up properly for Quicksilver development, create a new Quicksilver plugin project in Xcode, and get ready to start planning your plugin.
Continue Reading Anatomy of a plugin - Info.plist Part 1
The long awaited iClip 4 has been released and looks to be a great improvement over version 3. The GUI is extremely enhanced, and it “just works”. The animation effects are also the smoothest I’ve seen anywhere (I wonder if it’s Core Graphics?).
I’ll still be using Quicksilver’s Clipboard History (you know how much I love Quicksilver), but this iClip really takes things to a new level in ease of use and appearance. I can talk about it, but it’s probably better if you see it for yourself. Check it out.

Oops! What happened here?

Just goes to show what one little mistake in your code, or an unforeseen circumstance can do to your code. The file was only a few megabytes.
Remember kids, test your apps in every possible way, and then some. And encourage feedback.
Now, any ideas on what I can do for the next 230,000 years?