Internal commands in Quicksilver are essentially actions that don’t require a subject (direct object) defined by the user. Most tasks, such as “Force Catalog Rescan”, and some commands like “QS Preferences” are internal commands. The Clipboard plugin also adds a large number of internal commands so as you can see, they’re quite useful in some circumstances.
Continue Reading Writing internal commands for QuicksilverTag: Tutorial
Secret Quicksilver animation effects
You may have had a shot at creating a Quicksilver interface. (If you haven’t, see the tutorial). While it’s good fun to play with changing the colors and positions of the controls, there is a whole lot of really clever code in Quicksilver that lets you go beyond that and play with some weird and wacky effects on any window.
Continue Reading Secret Quicksilver animation effectsWrite your own Quicksilver interface
Writing your own interface for Quicksilver is surprisingly easy, especially if you have experience in Cocoa and Xcode. Having covered the basics about the QSPlugin key in the Info.plist, as well the as the fundamentals of writing Quicksilver actions using Xcode, we are ready to start in a completely new direction. The Quicksilver interface.
Continue Reading Write your own Quicksilver interfaceZap unwanted apps the Quicksilver way
AppZapper, the uninstaller Apple forget
, is a great way to remove applications along with any garbage files they may have left on your system in the form of preferences, caches, and application support. Using Quicksilver, removing an application with AppZapper is as easy as a simple hotkey or trigger.
Quicksilver replaces Terminal
Not only does Quicksilver replace Overflow, it can save you from having to constantly open the Terminal as well.
Continue Reading Quicksilver replaces TerminalNow this is hot Cocoa
It’s finished. The real craze and controversy over Disco’s smoke is over. Jonathan Wight was the first to write up an article on integrating the smoke effects into a third party Cocoa application. Times have changed, and the smoke framework bundled with the more recent versions of the application no longer produce the desired results by using the same code.
So how do you get any Cocoa application to start smoking? Austin Sarner was kind enough to reveal the usage and implementation of the changes to the Disco framework which allow a wider variety of Macs to experience the entertaining effect.
Continue Reading Now this is hot Cocoa![[RSS feed for this tag]](http://lipidity.com/wordpress/wp-content/themes/virtuoso/res/img/feed_tag.png)