On 19.06.2014 22:33, Joao S. O. Bueno wrote:
This is a missing feature in the 2.8 release. New features are usually not added
in stable release cycle, which is the case of gimp 2.8 - and gimp-python is
bound to it.
If it was something without which one would die - but the
functionality can be obtained by 5 lines
of code, as already answered in the first e-mail.
I will deal shortly with the other bug reported here - regarding the
"parent" atribute of layers, which
is being retrieved as Layer, not LayerGroup.
I might add the "export" method to GIMP Image objects - but that is a
new feature , I am not sure if it should be backported to 2.8 .
I think this is a bug, that this function is not exported, but I agree
with João about statement, that this function can be emulated so it's
not worth risking stability of 2.8 release by exporting it.
--
Vladimir Rutsky
On 19 June 2014 15:09, Ed . <ej_zg@xxxxxxxxxxx> wrote:
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: How to call gimp_export_image() from
Pythonplugin
On Wed, Jun 18, 2014 at 9:52 PM, Joao S. O. Bueno <gwidion@xxxxxxxxx> 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
_______________________________________________
gimp-developer-list mailing list
List address: gimp-developer-list@xxxxxxxxx
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
_______________________________________________
gimp-developer-list mailing list
List address: gimp-developer-list@xxxxxxxxx
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
