Moving to peas for plugin management

[Claudio Saavedra <csaavedra gnome org>]

Hi,

I'm currently porting eog to use libpeas for plugin management. libpeas
is now a blessed external dependency and other modules in the GNOME
Desktop have already done so, so it's a good chance to 1) get rid of our
EogPlugin code and 2) break the plugin interface and provide something
more appropriate for eog plugins.

So far, I've ported the existing plugins under plugins/ to implement the
PeasActivatable interface. This is enough for these plugins. However, I
think it might be useful to think of creating new interfaces and adding
new extension points in the eog core, that might make the application
more extensible. If there's anything that you are missing as a plugin
developer, this is a good time to let us know.

One issue is that python plugins will not work immediately. This is
something to investigate, as we probably need to add introspection
support to eog first.

This port is intended for 3.0 only. For 2.32 I think we should just ship
the current engine. This way, there will be enough time to port all the
plugins.

I put the patches in bugzilla:
https://bugzilla.gnome.org/show_bug.cgi?id=626091


Claudio

-- 
Claudio Saavedra <csaavedra gnome org>