Installing plugins in Griffon is pretty easy. You just type something like
% griffon install-plugin [plugin-name]
in your application’s base directory and it does all the rest. The actual plugin stuff gets put in ~/.griffon/<version>/projects/<appname>/plugins. But what if you want to develop a plugin and don’t want to have to reinstall with every little code and test change?
Well, Josh Reed has a nice blog post on exactly how to do that. I won’t recap it here, just say that essentially you nuke the installed stuff under the .griffon directory and make a symbolic link to your plugin development directory.
There are just two things that are a little confusing about it.
- How do you install a plugin in the first place so you can do the nuke and symbolic link thing in the first place?
- Why doesn’t your plugin show up as installed when you run
griffon list-plugins?
Well, the answer to the first question is simple. Simply package your plugin by going going to it’s base directory and typing
% griffon package-plugin
to generate a zip file. You can then navigate to your application’s base directory and type
% griffon install-plugin [path to plugin]/plugin-name-0.1.zip
all assuming that your plugin is version 0.1. After that you are good to go with Josh’s original instructions.
As for the second question, I’m still spelunking through the gant scripts to figure that one out.
