<span class="gmail_quote">On 9/12/06, <b class="gmail_sendername">Raphaël Slinckx</b> <<a href="mailto:raphael@slinckx.net">raphael@slinckx.net</a>> wrote:</span><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Good stuff. I remember on IRC you mentioned you couldn't be bothered to<br>> copy bits of Gabble and modify it... I'd love to see some work on trying<br>> to work out which are the common bits, maybe move stuff over to
<br>> GInterfaces or base classes as possible, and spin out a libgtpcm (glib<br>> telepathy connmgr) or something more catchy... :)<br>><br><br>I need first to understand the whole gabble build system, because it's
<br>hard to tell what's generated, from where, when, why, what's not, etc :)<br><br>Then i guess what'd be useful is something like we have for<br>telepathy-python, providing base classes for all the relevant objects,<br>
with sometimes a generic implementation for the methods. Also i guess<br>all the .manager voodoo, with the extractor from the dbus method to<br>generate it, and all the ParamSpecFooBar i've seen in gabble. I guess<br>also all the debug stuff, the persist flag and all that kind of common
<br>stuff could be pushed in that lib. If it's ok for gabble to depend on it<br>of course.<br><br></blockquote></div><br>That is what tapioca-core-glib is all about, check out <br><a href="https://svn.sourceforge.net/svnroot/tapioca-voip/trunk/tapioca-glib">
https://svn.sourceforge.net/svnroot/tapioca-voip/trunk/tapioca-glib</a><br><br>