If you can code, you can help us improve Gloobus. As you might not know, Gloobus is very extendable by the use of plugins so you could create your own to add a functionality to Gloobus. Here you’ll find instructions on how to get involved with Gloobus.
You can help gloobus in three ways:
1. Donating.
2. Fixing bugs.
3. Developing your plugins and sharing them.
Fixing Bugs
For fixing bugs, you can ask for help in launchpad or directly to me at guitarboy000 [at] gmail.com or at irc room #gloobus at freenode.net. I’ll point you where to look for and how can it be solved.
Developing Plugins
The example plugin just loads an image using pixbuf and you can see a few things to consider.
iExample inherts from interface-image so it will must implement the virtual functions in interface-image. There is only one virtual funcion: get_pixbuf, so your plugin will only have to implement the funcion get_pixbux()
Then, you need to tell the plugin manager which mimetype your plugin can open:
plugin_filetype itself = { PLUGIN_NAME, "image/jpeg","image",1};
Here you define your plugin name, the mimetype it can open, the parent interface (image) and the priority (if there is more than one plugin for the same filetype). Just changing these few things (and the name of the class) you can have your plugin running perfectly, and of course, you can ask for help in launchpad or directly to me.
