Re: [Gimp-developer] How to call gimp_export_image() from Pythonplugin

["Joao S. O. Bueno" <gwidion gmail com>]

On 21 June 2014 18:02, Ed . <ej_zg hotmail com> wrote:
> "GIO is a file access library and part of GLib." -
> http://wiki.gimp.org/index.php/Hacking:Porting_file_plugins_to_GEGL_and_GIO#Porting_to_GIO
>
> GIR is "(GObject Introspection Repository)" -
> http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/
>
> GIR is something that GIMP will fully support when someone gets around to it
> - currently I've volunteered to be that guy.

So - that is "GIR", not "GIO".

How far had you got?


> Ed
>
>
> -----Original Message----- From: Joao S. O. Bueno
> Sent: Friday, June 20, 2014 11:59 PM
> To: Vladimir Rutsky
> Cc: Ed . ; gimp-developer
>
> Subject: Re: [Gimp-developer] How to call gimp_export_image() from
> Pythonplugin
>
> > What is GIO?
>
>
> It stands for "Gobject Introspection O<forgot>"
>
> It is a framework to,in a more or less automated form,  expose C functions
> and
> gobject based classes to various languages - including Python.
>
> The Python bindings for gtk+3.0 , ofr example, are GIO based -
> in this way, one does not have to re-especify every function or class
> one wants to expose to other languages in  a manually written C
> (or other configuration) file.
>
>
> Pygimp today has C modules which have to create Python objects that mimic
> GIMP objects, and all manipulations of these objects are wrapped by
> methods exposed
> to Python which in turn call one of the libgimp functions.
>
> With GIO, all libgimp functions could be called directly, and what we
> would need is an order of magnitude simpler implementation of the
> objects, directly in Python.
>
> I am working on such a layer for GEGL, for example -
> http://github.com/jsbueno/python-gegl
>
>   js