So it looks like the right-thing-to-do now is to add introspection
to Babl (otherwise we will need dirty workarounds in gegl).
js
--
On 12 February 2015 at 21:01, jcup...@gmail.com wrote:
On 12 February 2015 at 16:30, Joao S. O. Bueno gwid...@mpc.com.br wrote:
Otherwise, I think I will
On Fri, Feb 13, 2015 at 12:52 PM, Joao S. O. Bueno gwid...@mpc.com.br wrote:
Ok, if people are committed to it, that means it is not left
to die, and it is a matter of fixing it in GEGL (and GIMP soon).
I've been looking around, one problem seems to be that since BABL
has no introspection,
On 12 February 2015 at 20:50, Jon Nordby jono...@gmail.com wrote:
On 12 February 2015 at 06:30, Joao S. O. Bueno gwid...@mpc.com.br wrote:
Hi -
after several months I am taking back a look at my Python bindings for
GEGL,
which make use of gobject introspection.
The situation with gobject
On 13 February 2015 at 20:12, Jon Nordby jono...@gmail.com wrote:
On 13 February 2015 at 01:52, Joao S. O. Bueno
I've been looking around, one problem seems to be that since BABL
has no introspection, any functions relying on BABL parameters
(even just babl formats, which are ordinary C
On 13 February 2015 at 01:52, Joao S. O. Bueno
I've been looking around, one problem seems to be that since BABL
has no introspection, any functions relying on BABL parameters
(even just babl formats, which are ordinary C strings with
a fancy typedef) are not exported.
Daniel Sabo fixed
On 12 February 2015 at 16:30, Joao S. O. Bueno gwid...@mpc.com.br wrote:
Otherwise, I think I will rewire the python bindings using another
method to bridge to the C library, which is more predictive and better
supported.
I've made a Python binding for my largish C library using
