[Geany-devel] Another plugin interface

[joshua.rh at comcast.net]

Hello everyone,
       So I've been reading the list and it seems another plugin interface is desired.  I'd love to help because I'd like to write plugins in python (and maybe other languages eventually).  The issue is I'm not super experienced and I don't have loads of extra time.  I think the best way to do this (correct me if I'm wrong) would be in the open, designing it first so everyone can have a say before we go implementing things (that way we have the best  possible interface).
    Could we use libpeas for this interface? http://library.gnome.org/devel/libpeas/0.7/  It uses gobject and gedit uses it.  Having an interface that other projects use would be awesome because then we could port plugins between the two without too much effort.  Also there's the whole thing about when they fix bugs in the interface we get those fixes too.
    I'm not super fond of the libpeas interface right now (http://library.gnome.org/devel/libpeas/0.7/PeasGtkPluginManager.html), mainly because of the lack of tooltips, but I'm planning on patching that once I have some time and learn to use libpeas.  We could also make another interface, and we'd still benefit from having the same interface for the reasons above.
    The dependencies are an issue, as libpeas uses bleeding-edge stuff (gobject-introspection 0.10.1 which depends on other new stuff I believe).  But we could hook it in and then slowly port things to it (as mentioned in one of the plugin-quality messages).
    I apologize for the long-winded message, the tl;dr version is this:  I'd like to help with a new plugin interface, I think libpeas is a good candidate, and if we do the design out in the open n00bs like me might be able to follow/learn it and help later on :).  Thoughts?

Josh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geany.org/pipermail/devel/attachments/20110312/e1f372e4/attachment.html>