Le 07/07/2014 18:48, Thomas Martitz a écrit : > [...] > > In my last post I've followed the approach of proxy plugins, aka pluxys. > This approach is based on geanypy and implements a plugin API for > plugins to act as proxy. I have mostly finished that (including an > trivial example pluxy), and ported geanypy to this framework. The result > is that with this approach I was successfully able to load python > plugins with the core, including access to the plugin API, to the extend > that geanypy allows plus keybindings via a new (experimental) API call. > I think this should cover almost everything you would want for python > plugins. > > Since with that work you can successfully load python plugins I consider > this approach workable.
Nice. > Now that the pluxy approach is in the final stages I went onto toying > with libpeas. > > [...] > > There are three areas of problems with libpeas before we can adapt it, > two of which I could already solve in a fork. > > [...] If using libpeas really requires having a modified version of it lying in our code, I'm not convinced it's a great idea. Regards, Colomban _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel