Using Plugins with Gnome-Do (but for real)

I’ve been using Gnome-Do for a little bit (it’s a Quicksilver workarlike – like Launchy, which I had a brief love affair with before I gave up Windows), and love the fact that I can rapidly launch stuff that I don’t necessarily remember the capitalization of without having to resort to my mouse or move from home-row. So naturally I was thrilled when I found out it was extensible with plugins! Of course, I followed the instructions on the site (copy the plugin.dll file to /home/user/.local/share/gnome-do/plugins/) and restarted Gnome, and… nothing. No new functionality. So I kind of meandered around and found another suggestion on the Ubuntu wiki, to copy to your /home/user/.do/addins directory. WRONG AGAIN. So I decided to do a little mental leap and created a /home/user/.do/plugins directory, and lo there was Connect with SSH and Tweet. Hooray.

Hot tip to all you plugin folks out there, you could include instructions on how to install your plugins in the readme! It’d be like… 1996 and shit, with annotated instructions.

3 thoughts on “Using Plugins with Gnome-Do (but for real)

  1. User plugins go in ~/.local/share/gnome-do/plugins. ~/.do/plugins is the old location, so your copy of Do is out of date.

  2. No, my copy is up to date, which is to say, it’s the version from the repositories for Ubuntu (edited) Gutsy, and therefore, there should be doco on the old plugin location. Matter of fact, the more I look the more I note that there is zero documentation for this project (and don’t even get me started on the “source code _is_ documentation” argument) Other projects have successfully kept documentation for older revisions of their configuration for projects which are an order of magnitude *ahem*FreeBSD*ahem* more complex than a userspace app. I find it repulsive to think that the attitude of “your shit’s out of date” is the proper solution for such a simple documentation problem. For your edification, the Gnome-Do in Hardy seems to be up to date, using the newer location.

  3. Heretic! It is against the will of… something… to keep documentation in a hierarchy based on version. Or something.

    Also, I’m not a fan of software that shuffles around where it keeps conf files. It’s always messy.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.