[Telepathy] telepathy-glib GObjectIntrospection update

[Danielle Madeley]

Just FYI, this is being tracked in the following bug:

  https://bugs.freedesktop.org/show_bug.cgi?id=26249

And the branch has changed (separating my generated JS bindings from the
gobject-introspection work):

  http://git.collabora.co.uk/?p=user/danni/telepathy-glib.git;a=shortlog;h=refs/heads/gobject-introspection

On Thu, 2010-04-08 at 21:07 +1000, Danielle Madeley wrote:
> Some time ago I had a play with getting GObjectIntrospection working for
> telepathy-glib, and got very wedged. Well I've dusted this work off and
> started hacking on it again.
> 
> http://git.collabora.co.uk/?p=user/danni/telepathy-glib.git;a=shortlog;h=refs/heads/js
> 
> What works:
> 
>  - account manager and account preparation work, there is a very simple
>    am.js that prepares the valid accounts and gets the current presence
> 
> What doesn't work:
> 
>  - any other callback usage (e.g. tp_connection_call_when_ready); I'm
>    not sure what the error is here, I'm not sure how much time to spend
>    on it given that it's going to be replaced
> 
> Evil hacks:
> 
>  - there is a program called gir-scrubber.py which rewrites things I 
>    don't like in the generated GIR file, e.g. GArray_guint_
>  - the method calls in TpProxy don't work with introspection because 
>    their first argument is a gpointer, not a TpProxy* -- this is 
>    arguably a bug in the introspector -- it's currently worked around
>    using a proxy-introspectable.h
> 
> ToDo:
> 
>  - decide how to handle the D-Bus API. In order to take advantage of 
>    language features, I think it makes the most sense to use the
>    specparser to generate a D-Bus API per target, and somehow tie this
>    back in to Tp.Proxy. Thoughts appreciated.
> 


-- 
Danielle Madeley
Software Developer, Collabora Ltd.                  Melbourne, Australia

www.collabora.co.uk