Quicksilver <3s Backpack
Web services are going lowercase - Signal vs. Noise
Mashing Quicksilver and Backpack together to create an alternative interface for entering content. It’s very cool and it’s just the beginning.
David’s post points to a terrific Quicktime movie illustrating the kind of interaction you can generate when your small pieces are loosely joined—in this example using Quicksilver and email to seamlessly add items to a Backpack page. Totally slick.
It’s funny, but I still sometimes struggle to explain Quicksilver to people who haven’t seen it in real-world usage by someone who’s adapted their workflow to take best advantage of it—this movie is a great demonstration of how that looks for one person, so I recommend you check it out.
The mind-blowing thing about Quicksilver is how it allows you to adapt or massage your workflow down to a series of minimal movements. Since it can glue together virtually any content with almost any actions that that content can understand, it become like an Erector set for your workflow. It observes how you work and then lets you bind your most common activities to key commands and mouse gestures.
Yeah, yeah I know, most of you are already drinking the Kool-Aid, but I know there’s still a few of you out there shaking your heads. Check out the movie, and consider the small pieces you might want to loosely join.
[Link: Lifehacker]
- Merlin's blog
- 5423 reads

when, though, will we get...
when, though, will we get a quicksilver action for “send to backpack”?
…or, better and more flexible, i suppose, a way to turn applescripts or automator scripts into quicksilver actions, so we could roll our own?
(yeah, i realize you didn’t write quicksilver, merlin … just venting.)