Danni's branch with GObject Introspection also contains some auto-generated bindings into (one of the dialects of) Javascript. I consider this considerably lower-priority than the introspection work at the moment. http://git.collabora.co.uk/?p=user/danni/telepathy-glib.git;a=shortlog;h=refs/heads/js Implementation-wise, I'm not happy for telepathy-glib to grow a build-dependency on Cheetah, which blocks the current implementation of the Javascript part, although it's probably a good prototype to build on. telepathy-glib is relatively fundamental to Telepathy, so we should keep its build-dependencies somewhat light - that's why it avoids going outside the Python standard library for the codegen, and in particular why it doesn't use telepathy-python or dbus-python.
So, thinking about it the other day, there's no reason this work has to be part of tp-glib (if we decide to keep it at all once we have rich high-level API).
Do we really want this? The current plan seems to move to high level API for bindings.
Agreed. I'd suggest WONTFIX.
I also agree. High-level is a better solution and clearly the future of Telepathy. Additionally there are problems like ordering guarantees broken by having two connections to D-Bus.
WONTFIX it is then.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.