As a further update on my previous post about Jingle support, we’ve been progressing at a fairly rapid pace and as described in our Jingle branch wiki page we now have Jingle audio calls working both from Psi to Psi, and from Psi to and from Google Talk. Hopefully this means we’ve got the interface with libjingle working ok, and any other client that comes along using libjingle will interoperate just fine. We can but hope. Now that the linux code supplied with libjingle works, we’re looking at other platforms; first of all Mac OSX.
Please not that this is not a guarantee that the jingle branch is stable yet, it’s certainly not, but it’s getting better

Categories: Jabber, Psi
4 Comments »

Subsequent to my last post about the branches of Psi we’ve been working on, I’m now delighted to announce that we’ve also been working on a third branch in the recent weeks.

The Jingle protocol (session and voice) is the culmination of months of discussion between the Google Talk team and interested parties in the JSF, which finally became standards-track yesterday. Jingle is basically the voice protocol supported by the Google Talk client.

The Google Talk team today announced the first release of a C++ library which manages the Jingle protocol. This means that other clients should be able to take this code and integrate Jingle support without coding the p2p and other details themselves.

In the last month or so, Sean Egan (one of the nice guys on the GT team (yes, they rock)) has been helping Remko and myself integrate the libjingle code in Psi ready for libjingle’s release today, meaning……voice calling for Psi. This is where a lot of Remko and my time has gone which might otherwise have been spent on visible Psi development.

Since the libjingle library has been publically released now, we are able to give a first glimpse of our Psi branch using the library.

Also included (and a necessary pre-requisite to Jingle support), this is the first time you’ve seen Psi supporting Entity Capabilites (there’s a patch that’s been circulating that we’ve noticed some unofficial builders have been including but it’s broken (hey, sometimes there’s a reason patches don’t make it into mainline )). As such, if you just want to test caps, grab the repository and don’t enable jingle support when you compile. Unlike all the warnings further down the post about the stability of our interface with libjingle, the Caps support should be fine now and will be merged into mainline as soon as our rather hectic roadplan allows.

There are disclaimers:

• This is heavily unstable software
• This is not feature-complete
• This voice support, which doesn’t yet work reliably, is linux-only at the moment.

The state of the code at last glance was:

• Psi < -> Psi calling will not work. It will look like it does, but no stream will be established.
• Psi < -> Google Talk calling will work, but will terminate a short time afterwards (20 or 30 seconds)
• Psi < -> call calling should work ok. (call is the example command-line client in psi/third_party/libjingle/talk/examples/call. Just cd there, run qmake and then make)

So please feel free to have a play with what’s up there, and if you want to submit bug fixes, I’d be more than delighted, but don’t expect things to work properly yet.

The darcs repo is available at:

http://dev.psi-im.org/darcs/psi-jingle/

use ./configure --help to work out what you need, my line looks like this:

./configure --with-glib-inc=/usr/include/glib-2.0 --with-glibconfig-inc=/usr/lib/glib-2.0/include/ --with-ortp-lib=/usr/local/lib/ --with-ortp-inc=/usr/local/include/ortp/ --with-ilbc-inc=/usr/local/include/ilbc/ --with-ilbc-lib=/usr/local/lib --with-speex-inc=/usr/local/include/speex/ --with-speex-lib=/user/local/lib --enable-jingle

Please note that this development is parallel to the release series until it’s stable, when we’ll merge it back in.

/K

Categories: Jabber, Psi
13 Comments »

Psi development seems to have been pretty stagnant lately so here’s an update on what’s been happening in the world.

Psi-0.10

The story of 0.10 isn’t a happy one, unfortunately; it’s been dragging on for a very long time due to circumstances outside my control. I think the code’s ready. Most, if not all, of the translations are now in. Once we’ve got a new logo / icons ready, we’ll ship. Fortunately, while 0.10 has been stalled, we’ve branched the codebase and have been working on other things:

The Qt4 port

Assorted people have been working pretty hard on getting Psi ported over to the new Qt4 library; it’s turned out that this wasn’t as trivial as some people might have hoped but we’re progressing well. Psi’s now usable (in a basic state) on Qt4 and once we’ve got 0.10 out of the door the codebase should be ready for some very early public consumption. We’re taking the opportunity while porting to get some code rewriting done, so things will hopefully feel a little smoother as well.

Wishlists

Fran suggested to me that it’d be useful for contributers to have a list of things I’d like implemented that’s a bit nicer to scour than the bug tracking system, so I created a feature wishlist. The idea is that I’ll list here small, or self-contained units of code which’re useful to Psi, but not on the immediate roadplan for the core development team. I hope to add to this list and then maintain it so that anyone with a hankering to get some coding time in has some ideas, together with suggestions for implementation. If anyone has ideas that they think could be added to this list, please let me know and I’ll have a look at them.

Categories: Psi
Comments Off