From kopete-devel Fri Nov 05 16:54:19 2010 From: Duncan Mac-Vicar Prett Date: Fri, 05 Nov 2010 16:54:19 +0000 To: kopete-devel Subject: Re: Real Jingle (not libjingle) support in Kopete Message-Id: X-MARC-Message: https://marc.info/?l=kopete-devel&m=128897611209695 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0926609891==" --===============0926609891== Content-Type: multipart/alternative; boundary=20cf303b389d20287604945120ec --20cf303b389d20287604945120ec Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable 2010/11/2 Rafa=B3 Mi=B3ecki > Hey again, > > W dniu 5 kwietnia 2010 15:40 u=BFytkownik Rafa=B3 Mi=B3ecki > napisa=B3: > > Detlev, could you please tell us something about status of Jingle > > support in Kopete? > > > > I've checked new_jingle and it does not seem to be updated anymore. Is > > code in this branch ready to use? Can you merge it back to master > > branch of Kopete? > > > > http://techbase.kde.org/Schedules/KDE4/4.5_Feature_Plan#kdenetwork > > lists whole Jingle as "TODO", I guess something of that is however > > already implemented in new_jingle? > > If we can not finish new_jingle (it seems no one has time for this), > could we update libjingle inside Kopete? New version of libjingle > sounds like protocol compatbile, could you check this maybe? > BTW, not long time ago, I synced libiris from trunk into the jabber protocol plugin, and reorganized the tree so that it could be merged easier in the future. I can post the patch if I find it, and if someone is interested in applying & testing it. --=20 Duncan Mac-Vicar P. --20cf303b389d20287604945120ec Content-Type: text/html; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable 2010/11/2 Rafa=B3 Mi=B3ecki <zajec5@gmail.com>
Hey again,

W dniu 5 kwietnia 2010 15:40 u=BFytkownik Rafa=B3 Mi=B3ecki
<zajec5@gmail.com> napisa=B3:=
> Detlev, could you please tell us something about status of Jingle
> support in Kopete?
>
> I've checked new_jingle and it does not seem to be updated anymore= . Is
> code in this branch ready to use? Can you merge it back to master
> branch of Kopete?
>
> http://techbase.kde.org/Schedules/KDE4/4.5_Featu= re_Plan#kdenetwork
> lists whole Jingle as "TODO", I guess something of that is h= owever
> already implemented in new_jingle?

If we can not finish new_jingle (it seems no one has time for this),
could we update libjingle inside Kopete? New version of libjingle
sounds like protocol compatbile, could you check this maybe?


BTW, not long time ago, I synced libiris from trunk into the jabber<= br> protocol plugin, and reorganized the tree so that it could be merged
eas= ier in the future. I can post the patch if I find it, and if
someone is = interested in applying & testing it.

--
Duncan= Mac-Vicar P.





--20cf303b389d20287604945120ec-- --===============0926609891== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel --===============0926609891==--