[Telepathy] [jdev] [Standards] Using Jabber in a KDE game

[Olli Salli]

On Wed, Sep 10, 2008 at 2:09 AM, George Goldberg
<grundleborg at googlemail.com> wrote:
> On Fri, Sep 5, 2008 at 8:18 AM, Kleag <kleag at free.fr> wrote:
>> You convinced me to try telepathy :-)
>>
>> Should telepathy-qt from kdesupport be enough to develop ? The build system of
>> telepathy seems a bit complicated...
>
> Telepathy-qt from kdesupport would be enough, but it is a very
> low-level API. However, there is also tapioca-qt in kdesupport, which
> provides a much more Qt like API for doing telepathy stuff, so I'd
> recommend you have a look at that first and see if it provides what
> you need. (Also, feel free to come and bug people on #decibel on
> irc.freenode.net about telepathy-qt or tapioca-qt).
>

If you don't mind a dependency on Qt 4.5, the TelepathyQt4 library at
git://git.collabora.co.uk/git/telepathy-qt4.git (and the branches in
git://git.collabora.co.uk/git/user/oggis/telepathy-qt4.git, sadly
there's currently a lot of unreviewed code, which hasn't yet been
merged to master) could be interesting to you.

TelepathyQt4 has the following advantages compared with the kdesupport
telepathy-qt:
- Saner code generation, written in pure python
- Production-ready API/ABI stability
- Additional DBus APIs can be built as extensions in applications
- Doxygen documentation (partially derived from the specification docstrings)

In addition to just the 1:1 mapping of the DBus interfaces as provided
by master and the kdesupport telepathy-qt, the branches in my personal
telepathy-qt4 repository also provide high-level Channel and
Connection objects with a lot of convenience functionality (most
importantly, automatically inspecting and tracking the remote object
state). This functionality should be merged to master fairly soon.

However, as TelepathyQt4 is still very much a work in progress (an
initial release will only happen after Qt 4.5 is released), it's up to
you which one to use.

-- 

Br,
Olli Salli