| | 1 | # Why Quicksilver |
| | 2 | |
| | 3 | I've been a Quicksilver[1] user for a long time, and I've always wanted to contribute but felt overwhelmed by the complexity of the platform, and the fact that I'm not all that good at writing objective-c. |
| | 4 | |
| | 5 | => https://qsapp.com/ [1] Quicksilver |
| | 6 | |
| | 7 | As just a user, I've depended on the goodwill of others to keep the app alive, and the plugins maintained. Now I want to make a change and help keep the app relevant for myself and others by learning how to develop plugins and adding functionality that is useful for myself and others, and by using this experience to make it easier for others to do the same. |
| | 8 | |
| | 9 | I could just as easily change to one of the other for-profit launchers out there, but I don't think any of them get close to the power and convenience that the "direct object" -> "action" -> "indirect object" provides. |
| | 10 | |
| | 11 | So why continue to use quicksilver, and why develop for it at all? Because I like it. I like the concept, I like the openness, and I want to give back. |
| | 12 | |
| | 13 | I'll be posting a series of posts on developing plugins for quicksilver as I learn. I started with a UI called Flat Bezel[2] that has involved mostly reading and building upon an existing interface[3], but I want to dive deeper and let others follow how this experience goes. |
| | 14 | |
| | 15 | => gemini://gemini.unlimited.pizza/flat_bezel.gmi [2a] Flat Bezel qsplugin @ gemini |
| | 16 | => https://unlimited.pizza/flat_bezel.html [2b] Flat Bezel qsplugin @ https (if you want to look at images) |
| | 17 | => https://github.com/mikker/YosemiteInterface-qsplugin [3] YosemiteInterface-qsplugin |
git.r.bdr.sh / rbdr / blog.unlimited.pizza / blame_incremental