GObject.Parameter

Olivier Crête olivier.crete at collabora.com
Fri Jan 11 16:50:17 PST 2013


Hello,

The whole GObject Introspection thing is a bit of a disaster.

I added some APIs to try to make it work, but I can't properly test it
because I can't get make install to work on pygobject, and yes, you need
to patch it.

So first, apply the patches to pygobject from these bugs:
https://bugzilla.gnome.org/show_bug.cgi?id=684062
https://bugzilla.gnome.org/show_bug.cgi?id=684060
https://bugzilla.gnome.org/show_bug.cgi?id=684059

Then, try the new API in this branch:

http://cgit.collabora.com/git/user/tester/farstream.git/log/?h=gi-fixes

The API is fs_stream_set_transmitter_ht() and it takes the transmitter
parameters as a GHashTable, see the python example for how to use it...

I'm eager to hear about your progress

Olivier

On Thu, 2013-01-10 at 20:39 +0100, Yann Leboulanger wrote:
> On 12/29/2012 05:04 PM, Yann Leboulanger wrote:
> > On 12/29/2012 04:56 PM, Olivier Crête wrote:
> >> Hello,
> >>
> >> On Sat, 2012-12-29 at 16:09 +0100, Yann Leboulanger wrote:
> >>> I'm porting my python code to gobject introspection. I am blocked on the
> >>> set_transmitter() function, which require an array of GObject.Parameter
> >>> objects.
> >>>
> >>> But I'm not able to create those GObject.Parameter instances. How am I
> >>> supposed to get them?
> >>>
> >>> When I do p = GObject.Parameter(), I cannot set a name or a value to p.
> >>
> >> Yes, it's a known (and annoying) limitation of GObject introspection..
> >> Suggestions for a more bindable API would be appreciated.
> >
> > Unfortunatly I don't know GObject introspection enough for that. I guess
> > a set_transmitter_param(transmitter_name, name, value) is not an option
> > 'cause parameters are needed when creating the FsStreamTransmitter?
> >
> > maybe something like that: fs_stream_set_transmitter
> > (FsStream *stream,
> > const gchar *transmitter,
> > gchar *stream_transmitter_parameter_names,
> > gchar *stream_transmitter_parameter_values,
> > guint stream_transmitter_n_parameters,
> > GError **error);
> >
> > and I guess there is no workarround for the moment? I just have to wait
> > a solution is implemented?
> >
> > Thanks for your quick answer,
> 
> Hi,
> 
> Is there any news about this issue? Any plan to have a way to use this 
> function via introspection?
> 
> Thanks,

-- 
Olivier Crête
olivier.crete at collabora.com



More information about the Farstream-devel mailing list