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

["Ed ." <ej_zg hotmail com>]

It is not a PDB function, but a libgimp (C) function. Since pygimp can do 
gimpui stuff (also C functions), there is no conceptual reason why pygimp 
shouldn't also handle gimpexport (which is where gimp_export_image lives).

I thought that in Python it was straightforward to access C functions? This 
is simply a function that returns an integer, albeit one that uses the GIMP 
UI - which pygimp already can initialise.

-----Original Message----- 
From: Vladimir Rutsky
Sent: Thursday, June 19, 2014 6:24 PM
To: João Sebastião de Oliveira Bueno
Cc: Ed . ; gimp-developer
Subject: Re: [Gimp-developer] How to call gimp_export_image() from 
Pythonplugin

On Wed, Jun 18, 2014 at 9:52 PM, Joao S. O. Bueno <gwidion gmail com> wrote:
> IS it available throught the PDB?
> Most GIMP - Python functions are done via PDB, except pixel-region
> manipulation stuff.
> If it is not in the PDB, it is not availabl in GIMP 2.8 - the current
> GIMP Python structure has to
> special cases a lot of things to work aside from the PDB, and doing so
> is not minor stuff
> done inside a release cycle.
>
> Making the 3-4 above calls are straightforward - I see no reason to
> violate the principle of no new features inside a release to add this.
> In GIMP 2.10, the export feature will also have to deal with precision
> management, and besides this export function, a class of PDB calls
> dealing with precision needs
> to be added as well.

Joao, Ed,

so gimp_export_image() should be exported to Python though PDB (to all
plugins) or by writing custom export code as done for some functions
to export it only to Python?

--
Vladimir Rutsky