On Fri, 12 Jun 2009 13:08:10 +0100, Nick wrote: >On Fri, 12 Jun 2009 13:42:41 +0200 >Jonas Haag <jo...@jonashaag.de> wrote: > >> Am 12.06.2009 13:25, schrieb Nick Treleaven: >> So if we modified this to also be able to call a >> > function in the C plugin, perhaps that function could handle >> > looking up e.g. Python symbols in a script by name. >> Well, this doesn't solve the registration problem, does it? > >We would have a function to create a plugin-like object that the C >plugin could call, but Geany would still need the lookup function to >resolve symbols. > >One problem with this approach is that python plugins would only be >available after the PythonPlugins C plugin was loaded. IMO this might >be OK, or we could make Geany always load it if present.
Sounds OK to me. Alternatively, maybe some kind of proxy plugin could do the trick: this plugin is loaded by Geany as any other plugin, it provides the necessary symbols Geany expects, and then this plugin provides some interface to various real Python plugins by exporting the Geany API in Python and so this plugin acts as some kind of proxy between Geany and the Python plugins. Maybe I'm missing something, it's late and I don't know Python nor its bindings to C, so, might be I'm just dreaming :). Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc
pgpN754o7LH1X.pgp
Description: PGP signature
_______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
