From kde-core-devel  Mon Aug 05 03:07:43 2002
From: Justin Karneges <justin-qt () affinix ! com>
Date: Mon, 05 Aug 2002 03:07:43 +0000
To: kde-core-devel
Subject: Re: KDE Jabber Library
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=102851712821921

Hi guys,

This thread sure got long!  Thanks for all of the comments.

To clarify:

Yes, libpsi is a Qt-based library for now.  My proposal was to turn it in=
to a=20
KDE lib for kdelibs.  I haven't done that yet because, well, I wanted to =
see=20
what kind of response I'd get first :)  Btw, this would be very easy I th=
ink. =20
KExtendedSocket, KSSL, and KVcard (is there such a thing?) are probably a=
ll=20
that will be substituted in.

While I do find the open vs proprietary IM debate interesting (and I have=
 a=20
strong opinion there), I believe it is irrelevant to the inclusion of lib=
psi=20
into kdelibs.  You see, Kopete already uses libpsi.  So from a=20
Kopete-developer perspective, moving libpsi into kdelibs is basically=20
equivalent to moving 10% (or so) of Kopete into kdelibs.  libpsi is=20
near-ready now, so I say let's put it in.  Moving the remaining 90% of Ko=
pete=20
can be left open for future debate.

Remember, libpsi is just a simple lib.  No dcop, no UI, etc.  No code wou=
ld be=20
removed if there ever was a libkopete in kdelibs, only added.

So what now?

Oh, and a final question:  why wait for KDE 3.2 ?  Is it too late to add =
a=20
functioning lib to 3.1?  I actually proposed this lib for KDE back in Apr=
il,=20
before the freeze, and it isn't going to change much from here-on out.

-Justin