Kopete socket timeout watcher
Hi Roman, this bug has been opened for a while now https://bugs.kde.org/show_bug.cgi?id=198789 . The iris library manages the connection itself and periodically checks if it is up. Do you think we should remove the socket timeout watcher from the XMPP protocol ? Cheers, Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: Real Jingle (not libjingle) support in Kopete
On Monday 05 April 2010 15:40:39 you wrote: > Hi, > > Detlev, could you please tell us something about status of Jingle > support in Kopete? Yes, the XMPP part works (or at least worked) what needs work is the multimedia part (especially the RTP part) > 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? I really don't have time with school :( > 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? The right status would be "IN PROGRESS". Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: facebook contacts not in group
On Tuesday 16 February 2010 21:43:09 Markus wrote: > Facebook forces its Friend Lists into Jabber groups. The only way to > properly work around this would be to have an option in Kopete's Jabber > plugin to ignore server-side groups. Too bad we don't have that option. > In the meantime I sorted my FB friends into Lists that match my Kopete > organization style. > I don't see the point in bypassing a standard protocol to adapt to services that don't respect the protocol. If you want that to be configurable, make a request to Facebook, we can't adapt to every buggy service out there. Detlev. > > Am Dienstag 16 Februar 2010 18:04:55 schrieb Dhaval Patel: > > I am able to connect Kopete to Facebook that via the Jabber plugin. The > > problem is that the contacts do not show up in any group. I created a new > > group called "Facebook" and drag contacts there but the next time I > > restart Kopete, they are in the root level and not the group. > > > > I also do not see that group until I right click on one of the contacts > > and go to Move To (I see the Facebook is selected) but I click on it > > again and the Facebook group appears with that contact. I can then drag > > other contacts into it. This is something I have to do everytime Kopete > > starts and every new person that logs in since it started. > > > > Am I doing something wrong? > > > > > > Thanks, > > Dhaval > > > > ___ > > kopete-devel mailing list > > kopete-devel@kde.org > > https://mail.kde.org/mailman/listinfo/kopete-devel > > ___ > kopete-devel mailing list > kopete-devel@kde.org > https://mail.kde.org/mailman/listinfo/kopete-devel signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: Kopete with Facebook XMPP
On Thursday 11 February 2010 09:03:47 Ramon Antonio Parada wrote: > I get a "XMPP 1.0 is required" error message. Maybe only works in KDE > 4.4, not it 4.3 that I'm using. > > On Thu, Feb 11, 2010 at 6:18 AM, Bruno Bigras wrote: > > Instructions for others client are on > > http://www.facebook.com/sitetour/chat.php > > > > If you didn't create a facebook username yet (to get the > > facebook.com/yourname or something) go to > > http://www.facebook.com/sitetour/chat.php . You need one to connect. > > > > my_fb_usern...@chat.facebook.com > > SSL : un-checked > > > > everything as default, and it works. > > > > 2010/2/10 Dhaval Patel : > >> Can you please list your settings? > >> > >> Here are mine. > >> > >> - Jabber ID: fbusern...@chat.facebook.com > >> - Use protocol encryption: Un-checked > >> - Allow plain-text password authentication: Checked > >> - Override default server information: Checked > >> - Server: chat.facebook.com > >> - Port: 5222 > >> > >> > >> Thanks, > >> Dhaval > KDE 4.3 Must be OK. Use all defaults. Don't override the domain name : use the jid : usern...@chat.facebook.com. Facebook asks to disable the "Allow plain text login" but it works both ways. Detlev Casanova. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: Kopete with Facebook XMPP
On Thursday 11 February 2010 01:09:27 Peter Saint-Andre wrote: > On 2/10/10 4:41 PM, Dhaval Patel wrote: > > I know, I tried to use it too and it did not work for me either. That is > > why I am trying to use this. Since they claim to support standard > > protocols I would think it is something Kopete could support. > > Don't panic. It's probably a bug in the Facebook XMPP implementation, > which is actually a gateway or client connector of sorts (they don't > have a native XMPP chat system). It will probably get worked out > sometime in the relatively near future... Well, it works for me. Maybe it's already been fixed. Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: info for feature guide!
On Saturday 30 January 2010 20:53:28 Jos Poortvliet wrote: > Guys & girls, > > The marketing team needs your help: we're not sure if the features > below did make it in the upcoming release of Kopete. Please let me > know if they did and explain where needed - I don't understand the > telepathy tubes sharing plugin and the akonadi logger... > > TODO Kopete UPnp Support Matt Rogers > TODO Kopete Jabber Jingle video support Detlev Casanova > > TODO Kopete Jabber Jingle ICE support Detlev Casanova > > TODO Kopete Add support for urls to Bonjour plugin Friedrich W. H. > Kossebau > TODO Kopete Rich text support for ICQ Roman Jarosz > IN PROGRESS Kopete Contacts plasmoid Dennis Nienhüser > IN PROGRESS Kopete Telepathy protocol plugin > George Goldberg > > IN PROGRESS Kopete Telepathy Tubes Desktop Sharing plugin George > Goldberg > IN PROGRESS Kopete Akonadi Logger(modify the history plugin) Kaushik > Saurabh > > > Cheers and tnx, > > Jos Poortvliet > (your friendly kde marketing dude) Why did I receive this mail just right now ? It's 11 days old :s Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
IRC support
Hi, Recently, you said you were working on a brand new IRC protocol implementation for Kopete. Are you still working on that ? If yes, where do you keep that code, do you need any help ? :-) Cheers, Detlev Casanova. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: STARTTLS support for XMPP?
On Tuesday 15 December 2009 22:06:37 Peter Saint-Andre wrote: > On 12/15/09 2:00 PM, Detlev Casanova wrote: > > On Tuesday 15 December 2009 21:49:03 Peter Saint-Andre wrote: > >> A year or two ago we discussed STARTTLS support for XMPP, so that Kopete > >> users can connect to the standard port 5222 and upgrade that connection > >> to TLS encryption. Is this supported yet? We will soon turn off port > >> 5223 at jabber.org and I don't want to leave Kopete users in the cold. > > > > Yes it is. > > OK, super. Thanks for the clarification. Is there a minimum version of > Kopete that I should recommend? It is supported since Kde 4.1, I think, but the latest version always recommended (currently 4.3.4). As Kopete got a lot more stable since Kde 4.2.0, I'd recommend that version as a minimal requirement. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: STARTTLS support for XMPP?
On Tuesday 15 December 2009 21:49:03 Peter Saint-Andre wrote: > A year or two ago we discussed STARTTLS support for XMPP, so that Kopete > users can connect to the standard port 5222 and upgrade that connection > to TLS encryption. Is this supported yet? We will soon turn off port > 5223 at jabber.org and I don't want to leave Kopete users in the cold. Yes it is. Cheers, Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] KDE/kdenetwork/kopete/protocols/jabber/googletalk [POSSIBLY UNSAFE]
On Saturday 21 November 2009 14:30:24 Urs Wolfer wrote: > On Saturday 21 November 2009 13:50:48 Pali Rohár wrote: > > On So 21. November 2009 13:25:41 you wrote: > > > On Saturday 21 November 2009 10:29:15 Pali Rohár wrote: > > > > SVN commit 1052235 by pali: > > > > > > > > imported google libjingle from > > > > http://libjingle.googlecode.com/svn/trunk revision 7 > > > > > > > > > > > > A libjingle (directory) > > > > AMlibjingle/AUTHORS > > > > AMlibjingle/COPYING > > > > AMlibjingle/ChangeLog > > > > A libjingle/DOCUMENTATION > > > > AMlibjingle/INSTALL > > > > > > [...] > > > > > > > http://websvn.kde.org/?view=rev&revision=1052235 > > > > > > Why? Please depend on this lib, do not include it. Think of what would > > > happen when we would copy every external lib into KDE svn... > > > > Google libjingle from http://libjingle.googlecode.com/svn/trunk is for > > gcc 3.3 (cant compile under gcc 4) and is too old (some years without > > update). It has a lot of bugs and doesnt work with Kopete-jabber without > > some patches. I commit this patch in rev. 1052317. > > Ok, I see. Still I do not like copying this lib into kdenetwork. I see atm > two possibilities: ask the developers of libjingle to release a new > version of the current svn snapshot with the patches (if they are not > active anymore, ask them to give the permission to you). Second you could > copy the lib into trunk/kdesupport (not absolutely sure if that would be a > correct way). I clearly prefer #1. This issue has already been discussed on Review Board before the commit. Please see http://reviewboard.kde.org/r/753/ . In a nutshell, libjingle is out of date and a release is expected anytime now. This version might not be 100% Jingle. An iris based implementation of jingle is being worked on in the svn://anonsvn.kde.org/home/kde/branches/work/kopete/new_jingle branch. Another good reading on this subject would be the Google Talk in kopete thread : http://lists.kde.org/?l=kopete-devel&m=125853434517208&w=2 I still think commits and Review Board should be linked somehow. > > It is not easy to depend on some lib, which must be patched before > > compiling and using. > > > > > Btw, why not "improving" Jabber, but add a new plugin for Google Talk? > > > > This is not plugin, but is is integrated to jabber protocol (rev. > > 1052230) > > Ah, very nice :) > > Bye > urs Cheers, Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Google Talk support in Kopete
On Saturday 21 November 2009 12:56:58 Rafał Miłecki wrote: > 2009/11/21 Pali Rohár : > > On So 21. November 2009 12:11:08 Rafał Miłecki wrote: > >> 2009/11/21 Pali Rohár : > >> > On So 21. November 2009 11:29:18 Markus wrote: > >> >> Small question: Is this only for GTalk accounts or can it be used > >> >> with any Jabber account as long as a compatible client (Kopete) is > >> >> used? > >> > > >> > It is only for accounts, which connect to jabber server > >> > talk.google.com > >> > >> Pali: please, don't use top-posting :) It's hard to track conversation > >> and quote/reply this way. > >> > >> Could you explain this limitation, please? > > > > This patch use external google libjingle call application > > (googletalk-call). Now it is imported from google svn repository to > > kopete-jabber. It start automatically after kopete-jabber successful > > login (and communicate throw I/O). This call application is only for > > GTalk accounts, because it use google specification and connecting to > > server talk.google.com. Maybe rewriting this application will be possible > > to use with other accounts. > > > > Other accounts cant login to google server, so you cant create voice > > call. But if you have GTak account, you can call to all contacts, which > > support google libjingle standard. I test it with windows version of > > Google Talk and Gmail voice web plugin. > > > >> I expected this feature working between any two clients supporting > >> googlified-jingle-standard. No matter what xmpp account is used, just > >> end-clients standard support based. > >> > >> So I thought it will be possible to talk in any scenario:: > >> k...@gmail.com <-> m...@gmail.com > > > > this works > > > >> k...@gmail.com <-> m...@xmpp.com > > > > if m...@xmpp.com doesnt use kopete, but other google libjingle client it > > works > > > >> sb_with_kop...@xmpp.com <-> m...@gmail.com > > > > this doesnt work > > > >> sb_with_kop...@xmpp.com <-> m...@xmpp.com > > > > this doesnt work > > Pretty clear now, thanks a lot :) You can test and play with the svn://anonsvn.kde.org/home/kde/branches/work/kopete/new_jingle branch, there is an implementation there (iris-based) which is (read : should) be compatible with every clients (but Google Talk) supporting Jingle. That's the aim, it does not work properly yet. Detlev Casanova. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Google Talk support in Kopete
On Wednesday 18 November 2009 09:50:18 Pali Rohár wrote: > Hello, > > finally I have libjingle Google Talk voice call support for Kopete. Patch > for Kopete jabber protocol is on http://reviewboard.kde.org/r/753/ > > For work this patch need googletalk-call application, which is on google`s > svn repository http://libjingle.googlecode.com/svn/trunk/ > > I convert automake files to cmake and now I can compile google`s libjingle > with kopete. > > So, can I now commit patch from reviewboard and import google libjingle > repository to kdenetwork/kopete/protocols/jabber/googletalk/libjingle ? > > I sending cmake patch and patch for google`s libjingle to fix crashed and > compile under gcc 4.3 / 4.4 > > I test it, and voice call works fine with windows Google Talk client and > Gmail web voice plugin. I'm ok with it but don't forget we're in Soft Feature Freeze Detlev Casanova. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: Add support for google libjingle voice call
> On 2009-10-19 12:48:58, Detlev Casanova wrote: > > I don't think that GMail will be upgraded to the Jingle standard soon so, > > you ship it ! :-) > > Pali Rohár wrote: > For support with gmail plugin I must change some code in google > libjignle. Trunk version in http://libjingle.googlecode.com/svn/trunk/ is for > old gcc and old libraries. This libjingle code works fine only if I applyed > patch from http://code.google.com/p/libjingle/issues/list . > > So If I can commit this patch for google talk voice support (which use > external executables), can I import google libjingle from > http://libjingle.googlecode.com/svn/trunk/ rev. 7 to kopete/jabber kde > repository with patches? With am2cmake I convert autoconf/automake to cmake > and now I can compile libjingle executables with kopete. > > Pali Rohár wrote: > Can I commit this patch now? > > Rafa? Mi?ecki wrote: > Detlev Casanova: you mailed me with link to > svn://anonsvn.kde.org/home/kde/branches/work/kopete/new_jingle on > kopete-devel. AFAIU this is going to be really used Jingle implementation in > Kopete soon. > > Doesn't that mean duplicated code? I mean potential Kopete's Jingle > implementation and what this patch adds. Maybe it would be better to get > svn://anonsvn.kde.org/home/kde/branches/work/kopete/new_jingle merged > mainline and then hack Kopete's implementation to work with Google's > modification of Jingle standard? No, and for 2 reasons : First, new_jingle would need lots of work and is not compliant at all with Google Jingle Secondly, Google will update their service to actual Jingle but it will have to wait a little longer and it won't be available before KDE 4.4 is released (or at least, hard freezed). So for KDE 4.4, let's have a Google Jingle implementation and, maybe, an actual Jingle implementation to be compatible with both implementation and for KDE 4.5, it will be OK to remove libjingle. - Detlev --- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/753/#review2712 --- On 2009-10-25 13:35:31, Pali Rohár wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/753/ > --- > > (Updated 2009-10-25 13:35:31) > > > Review request for Kopete and Detlev Casanova. > > > Summary > --- > > This patch add support (for jabber protocol) Google Talk libjingle voice > call. It use external libjingle "call" applicaion and stun server from > http://code.google.com/p/libjingle/ > > > Diffs > - > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/CMakeLists.txt 1040003 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.h > PRE-CREATION > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.cpp > PRE-CREATION > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.h > PRE-CREATION > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.cpp > PRE-CREATION > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.ui > PRE-CREATION > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.h 1040003 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.cpp 1040003 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.h 1040003 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.cpp 1040003 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgjabbereditaccountwidget.ui > 1040003 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/jabbereditaccountwidget.cpp > 1040003 > > Diff: http://reviewboard.kde.org/r/753/diff > > > Testing > --- > > It works fine with call application from http://code.google.com/p/libjingle/ > with patches from http://code.google.com/p/libjingle/issues/list installed in > PATH > > I try it with windows version of Google Talk (on windows) and voice call > works. I can make call, accept/reject incoming call, hang up call. > > I try it with windows gmail voice/video plugin and voice call works fine. > > > Thanks, > > Pali > > ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Sound problems...
On Wednesday 21 October 2009 16:04:31 Larry Shields wrote: > Has anyone had a problem in getting the sound to work using Kopete, > if so could you share with me as to what I need to install, to get the > sound working... Ahem, Kopete is an IM application, what are you trying to do ? Do you mean you want to have an audio chat ? In that case, which protocol do you use ? Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: Add support for google libjingle voice call
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/753/#review2712 --- I don't think that GMail will be upgraded to the Jingle standard soon so, you ship it ! :-) - Detlev On 2009-10-17 08:39:05, Pali Rohár wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/753/ > --- > > (Updated 2009-10-17 08:39:05) > > > Review request for Kopete and Detlev Casanova. > > > Summary > --- > > This patch add support (for jabber protocol) Google Talk libjingle voice > call. It use external libjingle "call" applicaion and stun server from > http://code.google.com/p/libjingle/ > > > Diffs > - > > trunk/KDE/kdenetwork/kopete/protocols/jabber/CMakeLists.txt 1000543 > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.h > PRE-CREATION > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.cpp > PRE-CREATION > > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.h > PRE-CREATION > > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.cpp > PRE-CREATION > > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.ui > PRE-CREATION > trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.h 1000543 > trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.cpp 1000543 > trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.h 1000543 > trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.cpp 1000543 > > Diff: http://reviewboard.kde.org/r/753/diff > > > Testing > --- > > It works fine with call application from http://code.google.com/p/libjingle/ > with patches from http://code.google.com/p/libjingle/issues/list installed in > PATH > > I try it with windows version of Google Talk (on windows) and voice call > works. I can make call, accept/reject incoming call, hang up call. > > I try it with windows gmail voice/video plugin and voice call works fine. > > > Thanks, > > Pali > > ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Request for updating Kopete_Jabber_Jingle
On Monday 12 October 2009 10:02:46 Anne Wilson wrote: > Thanks for including me in this conversation. As I don't subscribe to the > kopete-devel list, please keep me cc'd. Reply below quote: > > On Sunday 11 October 2009 22:52:52 Detlev Casanova wrote: > > On Sunday 11 October 2009 15:30:15 Rafał Miłecki wrote: > > > HI, > > > > > > I would like to ask you for updating > > > http://userbase.kde.org/Kopete_Jabber_Jingle > > > > > http://userbase.kde.org/Kopete_Jabber_Jingle has not been updated since > > KDE 3.5, this is not for KDE 4. > > But you're right, it should be updated. > > My immediate reaction was that I should use this statement to give a more > up- to-date page on userbase, but when I look at what exists I don't feel > competent. I suspect that quite a lot of that should be deleted, but I'm > not sure just what. That leaves us with two options. > > 1) Rafal or one of his associates could update the page directly > > 2) Rafal or teammate could give me a summary of what should be deleted, and > I'll create a page from the remains plus Rafal's comments, then ask them to > check it. Why Rafał ? _He_'s asking for an update. I planned on updating that page as soon as the branch is merged. > Either way, I'm happy to work with you all to get this corrected, and > thanks again for bringing it to my attention. Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Request for updating Kopete_Jabber_Jingle
On Sunday 11 October 2009 15:30:15 Rafał Miłecki wrote: > HI, > > I would like to ask you for updating > http://userbase.kde.org/Kopete_Jabber_Jingle > > Currently is says jingle is not supported, but on the other hand > http://techbase.kde.org/Schedules/KDE4/4.2_Feature_Plan lists jingle > voice as "DONE". Moreover starting Kopete I can see video preferences > (didn't try to talk with anyone yet). Hi Rafal, http://userbase.kde.org/Kopete_Jabber_Jingle has not been updated since KDE 3.5, this is not for KDE 4. But you're right, it should be updated. About Jingle, here's the deal : KDE 4.2 came with Jingle support. Unfortunately, The protocol was still at an Experimental state at the time and there were some bugs with the audio part of Kopete. So I decided to deactivate it for KDE 4.3 as the protocol was already outdated and no other client had this version implemented. There was also problems to connect through firewalls and routers. Now that the protocol has been stabilized, I've got a better and up-to-date implementation. It's available on the KDE SVN repository, there : svn://anonsvn.kde.org/home/kde/branches/work/kopete/new_jingle It's not ready yet (There is no Rtp and it's not been tested at all within Kopete) so I don't recommend to try it now. Rtp should be there soon, I just need to explain oRTP what it has to do :-) In Kopete, the webcam configuration dialog is used to configure your webcam for all protocols (currently, only Yahoo supports video though IIRC), That's why you can configure your webcam even if you can't use it. Detlev Casanova. PS:I'm not sure the e-mail addresses you used for Anne and Michaël are still valid but that's not a problem, I CC'd the answer to the kopete-devel mailing- list. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Kopete 1.0 and beyond
On Friday 02 October 2009 05:04:31 Matt Rogers wrote: > Hi, > > So, right now, the plan is to release Kopete 1.0 with KDE 4.4. If anybody > thinks that this shouldn't be done, then please speak up now so we can > change the plan. :) I've always wondered why Kopete isn't using the same numbering as KDE. I don't see the point of having multiple version number but if there is a good reason, then, I think it's a great idea to to release Kopete 1.0 :-) > For beyond Kopete 1.0, my current plan is to morph Kopete into the KDE > equivalent of GNOME's Empathy. This means converting Kopete to Telepathy. > As part of this conversion, I also would like to make use of the various > other kde4 technologies like akonadi, etc. I also want to resurrect > Decibel in the form of various Kopete components that are available > throughout the whole KDE stack for various purposes. The Telepathy plugin is promising, isn't it ? Would the Decibel resurrection make that not-really-born yet plugin a deprecated one ? Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] SocketTimeoutWatcher
Hi Roman, > there has been a lot of complains that protocols don't disconnect > themselves > when somehow connection is lost (or disconnect after long time). > > So after lot of googling I found linux only way how we can fix this. > There is TCP_INFO struct which contains info when last ACK was received > and when last data were sent and from this we can check if server still > gets packets from us. I don't really understand how the line if ( info.tcpi_last_ack_recv >= info.tcpi_last_data_sent && (info.tcpi_last_ack_recv - info.tcpi_last_data_sent) > mTimeoutThreshold ) works (sockettimoutwatcher.cpp:94). If the last ack received time it greater the the last data sent time, that means that the sent data has been acked, right ? So, why check the time difference btween those 2 and not the time difference between the last sent data time and the current time if the ack has not been received yet ? > This is all the code that needs to be add when we want to watch for > timeouts on some tcp based socket > > new SocketTimeoutWatcher(some_tcp_based_socket, timeout); > > I would like to put in into libkopete and add SocketTimeoutWatcher > to most protocols. I'll also add Q_WS_X11 to SocketTimeoutWatcher > so it doesn't break Win or Mac Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: Add support for google libjingle voice call
> On 2009-05-23 04:15:28, Detlev Casanova wrote: > > It's a good idea but will only be temporary. > > Google plans on updating their implementation as soon as the XFS jingle > > specifications are accepted by the XMPP council (should be any time soon, > > since a long time though). > > Pali Rohár wrote: > Will be later libjingle call example application works? > > Detlev Casanova wrote: > Yes, it should, but at that time (I hope before feature freeze for kde > 4.4) there will be a compatible implementation in libiris. > Currently, the spec changes too often to have an implementation which is > compatible for all clients. > > I don't know if Google folks are going to release a new libjingle version > and I don't know if it will be compatible. > > Pali Rohár wrote: > Can I commit this patch to svn now? Or it is something wrong with this? Support for the new Jingle standard will be ready quite soon. It should be added in Iris around the end of September. Also, Jingle standard is now at draft state. I'll contact Justin Uberti to know if Google will release a new version of libjingle or if it will be a totally different library. In this latter case, it should be best not to commit as it won't be compatible with a lot of other client when KDE 4.4 will be released. - Detlev --- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/753/#review1182 --- On 2009-07-21 15:08:07, Pali Rohár wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/753/ > --- > > (Updated 2009-07-21 15:08:07) > > > Review request for Kopete. > > > Summary > --- > > This patch add support (for jabber protocol) Google Talk libjingle voice > call. It use external libjingle "call" applicaion and stun server from > http://code.google.com/p/libjingle/ > > > Diffs > - > > trunk/KDE/kdenetwork/kopete/protocols/jabber/CMakeLists.txt 1000543 > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.h > PRE-CREATION > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.cpp > PRE-CREATION > > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.h > PRE-CREATION > > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.cpp > PRE-CREATION > > trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.ui > PRE-CREATION > trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.h 1000543 > trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.cpp 1000543 > trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.h 1000543 > trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.cpp 1000543 > > Diff: http://reviewboard.kde.org/r/753/diff > > > Testing > --- > > It works fine with call application from http://code.google.com/p/libjingle/ > with patches from http://code.google.com/p/libjingle/issues/list installed in > PATH > > I try it with windows version of Google Talk (on windows) and voice call > works. I can make call, accept/reject incoming call, hang up call. > > > Thanks, > > Pali > > ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Future of avdevice
On Tuesday 18 August 2009 11:45:20 Alex Fiestas wrote: > On Tuesday 11 August 2009 19:47:52 Detlev Casanova wrote: > > On Monday 10 August 2009 13:52:00 Will Stephenson wrote: > > > On Saturday 08 August 2009 21:44:10 Alex Fiestas wrote: > > > > After research a bit almost all sound capture architectures I'm sure > > > > which way we should take, the way of phonon! > > > > > > > > Phonon is designed and ready (I guess) to support capture, or at > > > > least this is what you can feel after read this: > > > > http://doc.trolltech.com/4.5/phonon- overview.html > > > > > > > > So, this is what I'm going to try to do, continue the work that > > > > taupter started months ago. > > > > > > > > I've studied how libav/v4l2 works, and I've some new code running > > > > etc, so I'm not starting from 0. > > > > > > Excellent news and a very brave move. Are you in contact with the > > > Phonon developers? > > > > > > Keep us posted on your progress! > > > > From what I know, Phonon is in this current status : > > The experimental branch API (the KDE Phonon) is capture-ready but needs > > lots of efforts especially in the different plugins. (I got that from > > Mathias Kretz, Phonon maintainer, > > http://mail.kde.org/pipermail/phonon-backends/2009- March/000270.html ) > > > > At Qt Software, they are trying to make Phonon become an abstraction of a > > device (I'm speaking about sound only here) and maybe not use the plugins > > for some tasks, it's not at all clear yet actually. That's for Qt 4.6 > > and I don't see at what point it is a good idea. (I got that from Justin > > McPherson on that thread : > > http://lists.kde.org/?l=kde-multimedia&m=124323207701000&w=2 ) > > > > Of course, that information is more than one month old so it may not be > > up to date at all :-). I haven't seen anything from Mathias Kretz in a > > long time now, I don't know if he's still working on the project. > > > > BTW, what in the Phonon overview makes you feel that phonon is ready to > > support capture ? > > > > Detlev. > > Thanks for the links and sorry for the delay, I have been a bit busy these > days :( > I felt that phonon is ready to have input because phonon is actually pretty > well abstracted, and is an impressive frontend for the backends, allowing > you to do whatever you want inside your backend. > > More or less the steps to implement the input in phonon are: > -Complete the experimental API. > -Implement that api in the frontends > > The first step is not really a big deal, I'll need help to decide a good > api, but after all is write an interface api. > Then, we've to "fill" that api in each backend, and here is where the hard > work reside... I'll start with the gstreamer backend, since this is the > only official linux backend that already have support for input (at least > for video because cheese is using it). So mainly what I'm going to do in > the next few days is learn gstreamer and how the gstreamer backend work in > phonon. > > Btw, in some days I'll send an email to the phonon mailist to get some > feedback, maybe I'm totally wrong or somebody else is working on that :p That's really what's missing in Phonon, there is also the problem of encoding, RTP, etc which must be decided. Getting sound from the audio card is something but applications will need speex encoded sound for exemple and maybe send it via RTP on the network. What should Phonon support ? What should applications implement ? You'll see that GStreamer can do all that, based on elements attached by pipes but other sound framework/engines might not. Those things have already been discussed at Akademy 2008 but never really came to a clue. I really don't have time right now (I did not study enough last year so my holidays are full of exams :-) ) but I can give you a hand. as I already used gstreamer in the past and have some experience in sound capture :-). Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Future of avdevice
On Monday 10 August 2009 13:52:00 Will Stephenson wrote: > On Saturday 08 August 2009 21:44:10 Alex Fiestas wrote: > > After research a bit almost all sound capture architectures I'm sure > > which way we should take, the way of phonon! > > > > Phonon is designed and ready (I guess) to support capture, or at least > > this is what you can feel after read this: > > http://doc.trolltech.com/4.5/phonon- overview.html > > > > So, this is what I'm going to try to do, continue the work that taupter > > started months ago. > > > > I've studied how libav/v4l2 works, and I've some new code running etc, so > > I'm not starting from 0. > > Excellent news and a very brave move. Are you in contact with the Phonon > developers? > > Keep us posted on your progress! From what I know, Phonon is in this current status : The experimental branch API (the KDE Phonon) is capture-ready but needs lots of efforts especially in the different plugins. (I got that from Mathias Kretz, Phonon maintainer, http://mail.kde.org/pipermail/phonon-backends/2009- March/000270.html ) At Qt Software, they are trying to make Phonon become an abstraction of a device (I'm speaking about sound only here) and maybe not use the plugins for some tasks, it's not at all clear yet actually. That's for Qt 4.6 and I don't see at what point it is a good idea. (I got that from Justin McPherson on that thread : http://lists.kde.org/?l=kde-multimedia&m=124323207701000&w=2 ) Of course, that information is more than one month old so it may not be up to date at all :-). I haven't seen anything from Mathias Kretz in a long time now, I don't know if he's still working on the project. BTW, what in the Phonon overview makes you feel that phonon is ready to support capture ? Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Kopete dev sprint
On Monday 10 August 2009 13:58:41 Will Stephenson wrote: > Hi all > > Although I'm currently inactive in Kopete development I would like to do > what I can to help it. > > I'm organising the KDE presence at the upcoming openSUSE conference and > would like this to take the form of sponsoring some upstream development > meetings on areas that are important to the distro at the conference. > > Would members of the current active Kopete team be interested in coming > together on a weekend in September in Germany to hack? > > Will Which weekend ? I might already be travelling a lot in september. Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Voice Capture for WLM
On Thursday 23 July 2009 20:46:49 Tiago Salem Herrmann wrote: > Hi, > > In order to be able to send voice clips in WLM I need to capture sound > from a microphone. > I've been searching how to do this using phonon, but as far as I can see > there is still no support for sound capture. > Does anyone have an idea on how I could do that in a good way and > platform-independent? > Is portaudio (www.portaudio.com) a good option? It can be, GStreamer is the best option currently, I think. The problem won't be cross platform, it will be Linux. Linux has multiple multimedia frameworks (GStreamer, PulseAudio, Jack,...) but some sound cards allow only 1 application to use it at a time. That means that if Kopete uses Portaudio and KNotify uses Phonon with GStreamer, one of them won't be able to play anything. Why I think GStreamer is the best is because (1) it's one of the engines used by Phonon and (2) most linux applications are using GStreamer. I hope Phonon will have support for audio Input and audio output from a buffer soon. Justin McPherson who works at Qt Software is working on Phonon to make it access the sound card directly (dropping media engines like GStreamer and Xine) but I haven't heard from that since some time now. But once again, programs using Phonon and programs using GStreamer will fight to have access to the sound card. The main argument for developping Phonon is that when you use Qt based applications (and so Phonon based), you should'nt use GStreamer based applications at the same time. This problem does not appear under Windows because all applications should use DirectX to deal with the sound card. Even GStreamer uses DirectX under Windows. But well, GStreamer is platform independant, very powerfull and is the most used. If you want an examaple library, see psimedia : http://delta.affinix.com/psimedia/ Cheers, Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Convert to git?
On Wednesday 15 July 2009 05:27:45 Matt Rogers wrote: > Hi, > > Is there any interest in being one of the first few projects that converts > from subversion to git? > > I know personally, that it would make it easier on me, since i'm already > using git-svn to interface with subversion most of the time anyways. I don't really know git yet but AFAICT, git is better when every "subproject" is using it together. Why should only Kopete start using git alone and not every project at the same time ? Anyway, I'm not against using git on Kopete at all :-) Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: Initialize deleted pointers to 0L to prevent crashes
On Tuesday 14 July 2009 23:31:00 Lamarque Vieira Souza wrote: > Em Tuesday 14 July 2009, Detlev Casanova escreveu: > > > On 2009-07-14 20:53:05, Detlev Casanova wrote: > > > > Please provide a patch > > > > Please provide a patch in > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris for all changes > > made in that directory. Read > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/README_BEFORE_COMMI > >TT ING before committing :-) > > Do you want me to open a new review request with the patch to libiris > alone or to commit the changes to libiris or both? I already have write > access to KDE's svn repository. No, just don't forget to add the patch, even if it is not on the same commit. > > (sorry for the double post, konqueror has troubles with the Review Board) > > > > > > - Detlev > > > > > > --- > > This is an automatically generated e-mail. To reply, visit: > > http://reviewboard.kde.org/r/1004/#review1597 > > --- > > > > On 2009-07-14 20:00:08, Lamarque Souza wrote: > > > --- > > > This is an automatically generated e-mail. To reply, visit: > > > http://reviewboard.kde.org/r/1004/ > > > --- > > > > > > (Updated 2009-07-14 20:00:08) > > > > > > > > > Review request for Kopete. > > > > > > > > > Summary > > > --- > > > > > > Initialise deleted pointers to 0L. Throughout all Kopete source code > > > pointers are deleted and not initialized, grep -r 'delete ' $(find \( > > > -name "*.cpp" -o -name "*.h" \) ) | wc returns 1105 lines, I can do a > > > rough estimation of at least half of those lines do not reinitialize > > > pointers. Althouth reinitialing pointers are not always necessary in > > > some cases it does is necessary and by what I have seen there are such > > > places in Kopete's source code. > > > Kopete::CommandHandler::slotExecFinished even passed one deleted > > > pointer to a function, which seems really wrong to me, it should delete > > > the pointer after calling the function, not before. To illustrate the > > > problem assume a is a class member pointer: > > > > > > delete a; // in one class method > > > > > > // In another class method: > > > if (a) // the result will the true even though a is deleted > > > do a->"something" // this can crash the application > > > > > > > > > Diffs > > > - > > > > > > /trunk/KDE/kdenetwork/kopete/libkopete/kopetecommandhandler.cpp > > > 993925 > > > > > > /trunk/KDE/kdenetwork/kopete/protocols/groupwise/libgroupwise/coreproto > > >co l.cpp 993925 > > > /trunk/KDE/kdenetwork/kopete/protocols/irc/irccontact_channel.cpp > > > 993925 > > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jingle/jinglertpsession.c > > >pp 993925 > > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/irisnet/core > > >li b/netinterface.cpp 993925 > > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp/jingle/ > > >ji nglecontent.cpp 993925 > > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp/jingle/ > > >ji nglesessionmanager.cpp 993925 > > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp/xmpp-co > > >re /parser.cpp 993925 > > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgahclist.cpp 993925 > > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgjabberregister.cpp > > > 993925 /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgregister.cpp > > > 993925 /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgsearch.cpp > > > 993925 > > > /trunk/KDE/kdenetwork/kopete/protocols/sms/smseditaccountwidget.cpp > > > 993925 > > > > > > Diff: http://reviewboard.kde.org/r/1004/diff > > > > > > > > > Testing > > > --- > > > > > > > > > Thanks, > > > > > > Lamarque signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: Initialize deleted pointers to 0L to prevent crashes
> On 2009-07-14 20:53:05, Detlev Casanova wrote: > > Please provide a patch Please provide a patch in /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris for all changes made in that directory. Read /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/README_BEFORE_COMMITTING before committing :-) (sorry for the double post, konqueror has troubles with the Review Board) - Detlev --- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/1004/#review1597 --- On 2009-07-14 20:00:08, Lamarque Souza wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/1004/ > --- > > (Updated 2009-07-14 20:00:08) > > > Review request for Kopete. > > > Summary > --- > > Initialise deleted pointers to 0L. Throughout all Kopete source code pointers > are deleted and not initialized, grep -r 'delete ' $(find \( -name "*.cpp" > -o -name "*.h" \) ) | wc returns 1105 lines, I can do a rough estimation of > at least half of those lines do not reinitialize pointers. Althouth > reinitialing pointers are not always necessary in some cases it does is > necessary and by what I have seen there are such places in Kopete's source > code. Kopete::CommandHandler::slotExecFinished even passed one deleted > pointer to a function, which seems really wrong to me, it should delete the > pointer after calling the function, not before. To illustrate the problem > assume a is a class member pointer: > > delete a; // in one class method > > // In another class method: > if (a) // the result will the true even though a is deleted > do a->"something" // this can crash the application > > > Diffs > - > > /trunk/KDE/kdenetwork/kopete/libkopete/kopetecommandhandler.cpp 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/groupwise/libgroupwise/coreprotocol.cpp > 993925 > /trunk/KDE/kdenetwork/kopete/protocols/irc/irccontact_channel.cpp 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jingle/jinglertpsession.cpp > 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/irisnet/corelib/netinterface.cpp > 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp/jingle/jinglecontent.cpp > 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp/jingle/jinglesessionmanager.cpp > 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp/xmpp-core/parser.cpp > 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgahclist.cpp 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgjabberregister.cpp > 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgregister.cpp 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgsearch.cpp 993925 > /trunk/KDE/kdenetwork/kopete/protocols/sms/smseditaccountwidget.cpp 993925 > > Diff: http://reviewboard.kde.org/r/1004/diff > > > Testing > --- > > > Thanks, > > Lamarque > > ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: Initialize deleted pointers to 0L to prevent crashes
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/1004/#review1597 --- Please provide a patch - Detlev On 2009-07-14 20:00:08, Lamarque Souza wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/1004/ > --- > > (Updated 2009-07-14 20:00:08) > > > Review request for Kopete. > > > Summary > --- > > Initialise deleted pointers to 0L. Throughout all Kopete source code pointers > are deleted and not initialized, grep -r 'delete ' $(find \( -name "*.cpp" > -o -name "*.h" \) ) | wc returns 1105 lines, I can do a rough estimation of > at least half of those lines do not reinitialize pointers. Althouth > reinitialing pointers are not always necessary in some cases it does is > necessary and by what I have seen there are such places in Kopete's source > code. Kopete::CommandHandler::slotExecFinished even passed one deleted > pointer to a function, which seems really wrong to me, it should delete the > pointer after calling the function, not before. To illustrate the problem > assume a is a class member pointer: > > delete a; // in one class method > > // In another class method: > if (a) // the result will the true even though a is deleted > do a->"something" // this can crash the application > > > Diffs > - > > /trunk/KDE/kdenetwork/kopete/libkopete/kopetecommandhandler.cpp 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/groupwise/libgroupwise/coreprotocol.cpp > 993925 > /trunk/KDE/kdenetwork/kopete/protocols/irc/irccontact_channel.cpp 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jingle/jinglertpsession.cpp > 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/irisnet/corelib/netinterface.cpp > 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp/jingle/jinglecontent.cpp > 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp/jingle/jinglesessionmanager.cpp > 993925 > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp/xmpp-core/parser.cpp > 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgahclist.cpp 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgjabberregister.cpp > 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgregister.cpp 993925 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/ui/dlgsearch.cpp 993925 > /trunk/KDE/kdenetwork/kopete/protocols/sms/smseditaccountwidget.cpp 993925 > > Diff: http://reviewboard.kde.org/r/1004/diff > > > Testing > --- > > > Thanks, > > Lamarque > > ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Webcam: Bad resolution
On Tuesday 23 June 2009 18:55:21 Jaroslav Reznik wrote: > On Tuesday 23 June 2009 18:46:40 Pali Rohár wrote: > > I'm using new ov519 driver from http://linuxtv.org/hg/~hgoede/gspca. Yes > > you understand me, with this new driver kopete show lower resolution as > > with ov51x-jpeg. > > > > This problem I have with a lot of applications (skype, mplayer, ...). I > > ask developer of this new version of driver ov519, and they write me, it > > is problem in applications. In cheese, I can choose resolution 640x480 > > and then it works fine, but in kopete I cant choose resolution. > > Ok, > I'll check it but I'm quite busy now :( I'd like to prepare clean libv4l > implementation, it means lot of code cleanup etc ... Hi Jaroslav, That clean implementation, will it break the current AVDevice API in Kopete or can I rely on that to get pictures from a webcam ? Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Jabber resources
On Monday 22 June 2009 22:42:29 Peter Saint-Andre wrote: > On 6/21/09 4:57 AM, Detlev Casanova wrote: > > On Saturday 20 June 2009 21:37:32 Jan Ritzerfeld wrote: > >> Am Samstag, 20. Juni 2009 schrieb Pali Rohár: > >>> Hello, > >>> if I chating with somebody throw jabber protocol and he change > >>> resource, all new messages from him are shown in new tab (or window). > >> > >> https://bugs.kde.org/show_bug.cgi?id=111537 > >> https://bugs.kde.org/show_bug.cgi?id=142650 > >> https://bugs.kde.org/show_bug.cgi?id=175078 > >> https://bugs.kde.org/show_bug.cgi?id=194808 > >> > >>> It is possible set up kopete to show all incomming messages from all > >>> jabber contacts resources to one tab? > >> > >> And to which address the outgoing messages should be sent? > > > > There is also the fact that some people want different chat windows for > > different resources. > > > > Maybe add an option to redirect messages from all contact's resources to > > the same chat window. > > IMHO, a good practice is this: after receiving a presence change from > your contact, send the next chat message to the contact's bare JID, not > a specific resource. If the resource is not specified, the server will send the message to the resource with the highest priority, right ? Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Jabber resources
On Saturday 20 June 2009 21:37:32 Jan Ritzerfeld wrote: > Am Samstag, 20. Juni 2009 schrieb Pali Rohár: > > Hello, > > if I chating with somebody throw jabber protocol and he change > > resource, all new messages from him are shown in new tab (or window). > > https://bugs.kde.org/show_bug.cgi?id=111537 > https://bugs.kde.org/show_bug.cgi?id=142650 > https://bugs.kde.org/show_bug.cgi?id=175078 > https://bugs.kde.org/show_bug.cgi?id=194808 > > > It is possible set up kopete to show all incomming messages from all > > jabber contacts resources to one tab? > > And to which address the outgoing messages should be sent? There is also the fact that some people want different chat windows for different resources. Maybe add an option to redirect messages from all contact's resources to the same chat window. Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] SmartCom new root CA certificate
Hi Thiago In order to have SSL encryption for XMPP in Kopete, we use the SmartCom root CA certificate present in KSSL's ca-bundle.crt file. Since some time ago, SmartCom have had a new root CA cert and XMPP servers are going to switch to that new one only soon. The problem is that that new root CA cert is not in KSSL's bundle. That means security errors messages when connecting to an XMPP server with SSL. (see http://xmpp.org/ca/developers.shtml and http://lists.kde.org/?l=kopete- devel&m=124347997826053&w=2 ) Would it be possible to add it to the bundle ? Cheers Detlev Casanova. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: Add support for google libjingle voice call
> On 2009-05-23 04:15:28, Detlev Casanova wrote: > > It's a good idea but will only be temporary. > > Google plans on updating their implementation as soon as the XFS jingle > > specifications are accepted by the XMPP council (should be any time soon, > > since a long time though). > > Pali Rohár wrote: > Will be later libjingle call example application works? Yes, it should, but at that time (I hope before feature freeze for kde 4.4) there will be a compatible implementation in libiris. Currently, the spec changes too often to have an implementation which is compatible for all clients. I don't know if Google folks are going to release a new libjingle version and I don't know if it will be compatible. - Detlev --- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/753/#review1182 --- On 2009-05-23 02:33:43, Pali Rohár wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/753/ > --- > > (Updated 2009-05-23 02:33:43) > > > Review request for Kopete. > > > Summary > --- > > This patch add support (for jabber protocol) Google Talk libjingle voice > call. It use external libjingle "call" applicaion and stun server from > http://code.google.com/p/libjingle/ > > > Diffs > - > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/CMakeLists.txt 971715 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.h > PRE-CREATION > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.cpp > PRE-CREATION > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.h > PRE-CREATION > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.cpp > PRE-CREATION > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.ui > PRE-CREATION > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.h 971715 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.cpp 971715 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.h 971715 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.cpp 971715 > > Diff: http://reviewboard.kde.org/r/753/diff > > > Testing > --- > > It works fine with call application from http://code.google.com/p/libjingle/ > with patches from http://code.google.com/p/libjingle/issues/list installed in > PATH > > I try it with windows version of Google Talk (on windows) and voice call > works. I can make call, accept/reject incoming call, hang up call. > > > Thanks, > > Pali > > ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: Add support for google libjingle voice call
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/753/#review1182 --- It's a good idea but will only be temporary. Google plans on updating their implementation as soon as the XFS jingle specifications are accepted by the XMPP council (should be any time soon, since a long time though). - Detlev On 2009-05-23 02:33:43, Pali Rohár wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/753/ > --- > > (Updated 2009-05-23 02:33:43) > > > Review request for Kopete. > > > Summary > --- > > This patch add support (for jabber protocol) Google Talk libjingle voice > call. It use external libjingle "call" applicaion and stun server from > http://code.google.com/p/libjingle/ > > > Diffs > - > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/CMakeLists.txt 971715 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.h > PRE-CREATION > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalk.cpp > PRE-CREATION > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.h > PRE-CREATION > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.cpp > PRE-CREATION > > /trunk/KDE/kdenetwork/kopete/protocols/jabber/googletalk/googletalkcalldialog.ui > PRE-CREATION > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.h 971715 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.cpp 971715 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.h 971715 > /trunk/KDE/kdenetwork/kopete/protocols/jabber/jabbercontact.cpp 971715 > > Diff: http://reviewboard.kde.org/r/753/diff > > > Testing > --- > > It works fine with call application from http://code.google.com/p/libjingle/ > with patches from http://code.google.com/p/libjingle/issues/list installed in > PATH > > I try it with windows version of Google Talk (on windows) and voice call > works. I can make call, accept/reject incoming call, hang up call. > > > Thanks, > > Pali > > ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] kopete-4.2.2 and ortp-0.15.0
On Monday 27 April 2009 21:10:11 Mounir Lamouri wrote: > Hi, > > I'm the Gentoo maintainer of ortp and I would like to know if kopete is > working with the latest release of ortp (ie. ortp-0.15.0). At the > moment, ortp-0.13.1 is known to work with kopete-4.2.2 and kopete-4.2.2 > is compiling with ortp-0.15.0 but I didn't find anyone able to do a > run-test of kopete with ortp-0.15.0. > > So, do you have any successful case reported ? or is it even officially > supported ? > > Note that ortp-0.15.0 is officially breaking compatibility with older > releases because of rtp_session_recvm_with_ts() return value. Otherwise > my question has no reason. Yes, it's still compatible, rtp_session_recvm_with_ts() is not used, rtp_session_recv_with_ts() is used instead. Also, I tested with that version on gentoo amd64 and everything is fine. Cheers Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] chat window
On Wednesday 13 May 2009 15:48:40 Daniel Pelzl wrote: > ~/.kde/share/apps/kopete/styles/ > > and > > ~/.kde4/share/apps/kopete/styles/ > > are empty :/ > Try $KDEDIRS/share/apps/kopete/styles/ with KDEDIRS being the location of your kde 4 installation. On gentoo, it would be /usr/kde/4.2/ or /usr, on other distributions, I don't know. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] chat window
On Tuesday 12 May 2009 20:45:19 Dhaval Patel wrote:
> Whoa, I see your point. All the default themes have time only.
>
> http://kde-look.org/content/show.php?content=87567
>
> You can use the one I created, it looks like Gaim and shows you the
> date_time in a tooltip when you hover over a message. You can also hack one
> of the existing themes to show this information. I believe the Date is
> "%F". For instance, I use "%time{%F_%H:%M:%S}%".
Shouldn't all themes be updated so they all show the date too ?
In Psi, th date is shown only for offline messages (messages that are stored on
the server and that you receive when you connect to it). I don't know if
that's possible though.
Cheers,
Detlev.
signature.asc
Description: This is a digitally signed message part.
___
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] XEP-0234: Jingle File Transfer
On Friday 01 May 2009 03:02:09 Pablo Montepagano wrote: > I would like to know if you are planning on implementing that protocol for > Kopete, which would allow sending files to Gtalk users. It's not "planned" but it will be done anyway. the work has to be done in the Iris library first (it's being worked on). But it won't allow you to send files to GTalk's client users because it's still using an old version of the protocol (The Google jingle standard, even though I'm not sure if they have already upgrated that). Note that whith thelepaty support and gabble, it might work if you use the right version but I don't know which is the right version and I don't have any ETA... > I hope I'm not misusing this mailing list. Thank you very much for your > work. No, the mailing list is ther to ask questions. Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Webcam doesnt work
On Monday 20 April 2009 08:03:44 Pali Rohár wrote: > Hello, > some people have same problem: https://bugs.kde.org/show_bug.cgi?id=190082 Yes, people having this problem will have to wait KDE 4.3 which will have a kopete version with libv4l support. Cheers, Detlev. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: libv4l support for Kopete
> On 2009-03-09 14:55:57, Detlev Casanova wrote: > > Why not also use libv4l to do image conversion stuff ? Some formats are > > still not supported by Kopete (see bug > > https://bugs.kde.org/show_bug.cgi?id=186080 , this webcam only supports > > S561 and GBRG which aren't suported by kopete) > > Jaroslav Reznik wrote: > Sorry I was misleading you - the purpose of this patch is to support > image conversion, not v4l1 devices. Libv4l2 transparently converts from any > (known) pixel format to V4l2_PIX_FMT_BGR24 or V4l2_PIX_FMT_YUV420 where > necessary. So with libv4l2 enabled there's no need to do conversions in > Kopete code any more. Maybe libv4l should be required to build Kopete but I'm > not sure about its support around distributions. Ok, that I suppose that it means that when we will try to set a pixel_format, only V4l2_PIX_FMT_BGR24 and V4l2_PIX_FMT_YUV420 would succeed. As long as we only support V4l2_PIX_FMT_BGR24, it would be the one we will use and all the convertion code, the format trying code and the pixel_format enum could be removed, right ? - Detlev --- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/266/#review429 --- On 2009-03-10 01:33:23, Jaroslav Reznik wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/266/ > --- > > (Updated 2009-03-10 01:33:23) > > > Review request for Kopete. > > > Summary > --- > > This patch adds v4l support to Kopete's video device. Libv4l is wrapper > around v4linux so v4l2 apps can use transparent image conversion. See > attached bug. > > > This addresses bug 177338. > https://bugs.kde.org/show_bug.cgi?id=177338 > > > Diffs > - > > trunk/KDE/kdenetwork/kopete/CMakeLists.txt 937303 > trunk/KDE/kdenetwork/kopete/cmake/modules/FindLibV4L2.cmake PRE-CREATION > trunk/KDE/kdenetwork/kopete/config-kopete.h.cmake 937303 > trunk/KDE/kdenetwork/kopete/libkopete/avdevice/CMakeLists.txt 937303 > trunk/KDE/kdenetwork/kopete/libkopete/avdevice/videodevice.h 937303 > trunk/KDE/kdenetwork/kopete/libkopete/avdevice/videodevice.cpp 937303 > > Diff: http://reviewboard.kde.org/r/266/diff > > > Testing > --- > > > Thanks, > > Jaroslav > > ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Review Request: libv4l support for Kopete
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/266/#review429 --- Why not also use libv4l to do image conversion stuff ? Some formats are still not supported by Kopete (see bug https://bugs.kde.org/show_bug.cgi?id=186080 , this webcam only supports S561 and GBRG which aren't suported by kopete) - Detlev On 2009-03-09 08:18:29, Jaroslav Reznik wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/266/ > --- > > (Updated 2009-03-09 08:18:29) > > > Review request for Kopete. > > > Summary > --- > > This patch adds v4l support to Kopete's video device. Libv4l is wrapper > around v4linux so v4l2 apps can use v4l1 video devices. See attached bug. > > > This addresses bug 177338. > https://bugs.kde.org/show_bug.cgi?id=177338 > > > Diffs > - > > trunk/KDE/kdenetwork/kopete/CMakeLists.txt 937303 > trunk/KDE/kdenetwork/kopete/cmake/modules/FindLibV4L2.cmake PRE-CREATION > trunk/KDE/kdenetwork/kopete/config-kopete.h.cmake 937303 > trunk/KDE/kdenetwork/kopete/libkopete/avdevice/CMakeLists.txt 937303 > trunk/KDE/kdenetwork/kopete/libkopete/avdevice/videodevice.h 937303 > trunk/KDE/kdenetwork/kopete/libkopete/avdevice/videodevice.cpp 937303 > > Diff: http://reviewboard.kde.org/r/266/diff > > > Testing > --- > > > Thanks, > > Jaroslav > > ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] Chat window : video API
Hey, I made some thinking about how it would be nice to hadle video (a. k. a. video chat) in Kopete. Looking at Windows Live Messenger official client, Video is embedded into the chat window and you can't (apparently) hide it. It's a good idea because you can see only the person you are talking to and you don't have a lot of windows on your desktop. In aMSN, video is shown in another window. It's a good idea because you can have all video windows on top of other windows so you can see everybody at the same time. In Kopete, it seems that each protocol (currently, just Yahoo) has to manage that itself (by showing a video window like the old MSN plugin did) Mixing both ideas brings me to this : the video could be shown in a QDockWidget (or similar if there is one in kdelibs) created by the chat window so the Video could be attached to the chat window or floating all alone in it's own window. The API could be as simple as // Show the video widget, maybe remembering last QDockWidget::isFloating() // (Webcam chat has started) void showVideo(); // Hide the video widget (webcam chat is finished) void hideVideo(); // Set a QImage in the video widget (channel = Local for local video, // Remote for remote video) void setImage(const QImage& img, Channel c); That last one could be split in setLocalImage() and setRemoteImage(), it doesn't really matters. Of course, this QDockWidget could also get buttons to stop/start/pause video. Some other ideas I had : * Resizing the video window would resize the video (keeping ratio ?) * When closing the chat window : do we stop video or just detach the QDockWidget (would it still be there when the chat window is closed ?) ? For this point, both aMSN and WLM stop the video chat. * The widget could also manage everything related to audio chat (keeping stop/start/pause buttons but with a nice voice icon) * In WLM, the video can be resized in 3 different sizes, that could be used too. * Video could be shown everywhere the contact photo is shown (even thought it might be a little bit annoying seeing the video one more time each time a message is received.) * You might ask "Why not using Phonon for all that ?" Well, Phonon can't handle showing video (neither playing sound) from a buffer if it's not a QFile. So, I think that's pretty much it. Cheers, Detlev Casanova. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] kopete/protocols/sms/ui/empty.cpp
Hi, what is the use of this file ? Cheers, Detlev Casanova. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] Bad use of ChatMessagePart::formatName() ?
Hey,
There is a problem with the "is typing" notification in the chat window.
if a contact's name is , the name is shown correctly in
the ChatMessagePart but when the contact is composing a message, I am notified
in the bottom of the chat window " is typing a message..."
I had a look at the source code and found that the name is processed by
ChatMessagePart::formatName() before it is used. the second argument that is
passed to the function is Qt::PlainText and switching it to Qt::RichText
solves the problem (see the attached patch).
Is there any reason why Qt::PlainText is used instead of Qt::RichText ?
Also, the comment describing the method does not really tell what it does.
Does it change the text to "format" or does it return a printable text from a
text in "format" ?
Cheers,
Detlev Casanova
Index: chatview.cpp
===
--- chatview.cpp (revision 906281)
+++ chatview.cpp (working copy)
@@ -451,7 +451,7 @@
for( it = m_remoteTypingMap.begin(); it != m_remoteTypingMap.end(); ++it )
{
const Kopete::Contact *c = it.key();
- typingList.append( m_messagePart->formatName(c, Qt::PlainText) );
+ typingList.append( m_messagePart->formatName(c, Qt::RichText) );
}
// Update the status area
___
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Jingle jabber just jerked my jangle
On Monday 29 December 2008 13:44:48 Alan Jones wrote: > Hi All, > > I've been attempting to get repro on this > https://bugs.kde.org/show_bug.cgi?id=173205 This bug shouldn't be there anymore. > I've managed to get jingle support compiled in and it appears in the > config as you'd hope. > Though the start call options are disabled. The options are enabled if the other client is jingle and jingle raw UDP protocol version 0 compliant which is not widely implemented. > I was hoping someone would be able to give me an overview of where it > is and what's > expected to work, and the intended workflow. > > Could being behind a NAT router be effecting it? There is only Raw UDP currently, ICE-UDP support will be added later as it must be implemented in Iris before (but some book writing slows down the process a bit :) ) Raw UDP () means that you must not be behind a NAT. (or be on the same side of the NAT as the other client) Now, the purpose of the current Jingle Raw UDP implementation in the Iris copy in Kopete is to be able to try Audio and (after the exams) Video. Cheers, Detlev Casanova. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] New jingle support
On Tuesday 21 October 2008 01:31:05 Dâniel Fraga wrote: > On Mon, 20 Oct 2008 22:16:21 +0200 > > Detlev Casanova <[EMAIL PROTECTED]> wrote: > > Well, click the button :-) > > I also noticed a conflict with Skype. > > In Skype, my Sound In is: > > USB Device 0x46d:0x990 (plughw:U0x46d0x990,0) > > and on Jingle I have: > > USB Audio > > If I start Kopete with this setting, Skype is unable to > use the microphone. > > Any hints? Or is this a Skype problem? IIRC, Skype uses Jack to do sound stuff. I'm interfaced with alsa directly. When I use alsa, Jack has no access to the audio interface I'm streaming on. I'm considering using Jack too but I'm not sure it's the best solution, if anybody has advices about that, that would be great :-) Detlev Casanova ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] New jingle support
On Tuesday 21 October 2008 01:05:49 Dâniel Fraga wrote: > On Mon, 20 Oct 2008 22:16:21 +0200 > > Detlev Casanova <[EMAIL PROTECTED]> wrote: > > Well, click the button :-) > > Hi Detlev. When someone tries to call me, the user receives > something like that (translated): "It wasn't possible to make a call > because user is either using gmail chat or some other programa, not > gtalk". > Does gtalk knows I'm using Kopete and, for this reason, refuses > to make a call? As psa said, Google talk uses very old Jingle specifications, I tried to stay up-to-date with the Jingle specifications but they're still at a Experimental state so it's often changing and improving. Currently, I think Kopete is only compatible with Kopete as Goggle Talk should catch up soon and Telepathy Gabble (used by Pidgin AFAIK) is also using an old version of the specs (but they will catch up when jingle switches to Draft) Don't worry, it can only get better. Detlev Casanova. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] New jingle support
On Monday 20 October 2008 20:16:19 Dâniel Fraga wrote: > Hi! I'm glad to see that Jabber jingle support was commited to > svn. > > I have: > > ortp-0.13.1 > nice from git repository > speex 1.2rc1 LibNice is not necessary, I'll update the README file > But I don't see any changes in the GUI. How can I be sure that > my compilation has jingle support? Open a chat with a Jabber contact, there should be a "start jingle session" button there. You can also go to your account properties and modify some params in the Jingle tab. > How can I test it? Well, click the button :-) Cheers, Detlev Casanova. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] merging jingle branch in trunk
On Saturday 18 October 2008 04:09:36 Peter Saint-Andre wrote: > Detlev Casanova wrote: > > I'd to merge the soc-kopete-jingle branch into trunk before Sunday for > > inclusion in KDE 4.2 > > > > There is still no ICE-UDP support (that means that computer behind a NAT > > will not be able to establish a jingle session.) > > Have you investigated any of the ICE libraries, such as libnice? > > /psa Yes, but the ICE part shouldn't be the hardest, the sound part was the one which took me some time :-) As for using a library for ICE, I'm not quite sure yet as lots of these libraries use their own multimedia implementation and that would make Kopete unable to use Phonon when it has audio input possibilities (Microphone). Detlev Casanova. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] merging jingle branch in trunk
I'd to merge the soc-kopete-jingle branch into trunk before Sunday for inclusion in KDE 4.2 There is still no ICE-UDP support (that means that computer behind a NAT will not be able to establish a jingle session.) I work around that b getting the external IP address by HTTP (not standard and ports must be redirected to the computer.) Is adding a transport method authorize wile soft freeze of trunk ? Does anyone have any objections :-) ? Cheers, Detlev Casanova ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] systemtray.h:57: error: 'movie' was not declared in this scope
On Saturday 20 September 2008 23:44:48 Dâniel Fraga wrote: > On Sat, 20 Sep 2008 10:46:10 +0200 > > "Roman Jarosz" <[EMAIL PROTECTED]> wrote: > > Do you have recent kdelibs from trunk? > > No, I'm using kdelibs 4.1.1. > > But I'll install from trunk. Thank you! No, you can't do that, doesn't CMake fail ? You must use kdelibs from trunk to compile other packages from trunk. Cheers, Detlev. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] GSoC Status
On Tuesday 29 July 2008 16:54:54 Peter Saint-Andre wrote: > Detlev Casanova wrote: > > On Tuesday 29 July 2008 04:20:42 Peter Saint-Andre wrote: > >> Hi Detlev! > >> > >> Detlev Casanova wrote: > >>> A big part that I still have to implement is ICE-UDP. That's what will > >>> take the biggest part of the remaining GSoC time. > >> > >> Yes, ICE-UDP is big. Could you perhaps use a library for that? The only > >> one I know about is libnice. But I think that would be much easier than > >> building ICE support from scratch. > > > > That's what I think I'll do even though Iris guys won't be so happy about > > it because I think they'd prefer to have their own implementation. > > libnice looks... nice :) > > I also had a look at PJNATH but I really don't know which one to choose > > as I just discovered libnice. > > I am not a coder so don't listen to me about libraries, *but* in my > experience the developers of both libnice and PJNATH know what they're > doing, so I think you won't go too far wrong using either of those libs. > I'd be happy to put you in touch with the developers if needed. And if > you're not yet in my jabber contact list, feel free to add me (the JID > is [EMAIL PROTECTED]). I added you in my contact list last week ( [EMAIL PROTECTED] ) but I wanted to wait until summit was finished :) Detlev Casanova signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] GSoC Status
On Tuesday 29 July 2008 04:20:42 Peter Saint-Andre wrote: > Hi Detlev! > > Detlev Casanova wrote: > > Hey folks, > > > > After being in a bug hunting period in my code, I am back adding parts of > > Jingle ! > > Good news. :) > > > The first one is that I succeed sending and receieving RTP data for a > > Jingle session which has not been that easy as the documentation for this > > library is not easy to understand (I now know why I should comment my > > code :-) ) > > Which library do you use? I'm using oRTP, the linphone RTP library I don't know any other one. > > Also, the Jingle calls GUI can now have sessions added (that was the > > hardest part, the rest of the GUI should not be complicated. And when I > > say the hardest part, it was not so hard, it was just a copy-paste > > mistake which gave me a headache for 2 days...) > > > > Kopete will first be able to send a video file (using Jingle of course > > and using video via rtp). The video format will be theora and I will use > > that to make tests. > > > > In what concerns the sound part, I'll also start with a sound file. > > > > The reason I'll transfer files is that Phonon does not support inputs yet > > (No microphone and no video input even though Video input and video > > widget are coming). > > > > A big part that I still have to implement is ICE-UDP. That's what will > > take the biggest part of the remaining GSoC time. > > Yes, ICE-UDP is big. Could you perhaps use a library for that? The only > one I know about is libnice. But I think that would be much easier than > building ICE support from scratch. That's what I think I'll do even though Iris guys won't be so happy about it because I think they'd prefer to have their own implementation. libnice looks... nice :) I also had a look at PJNATH but I really don't know which one to choose as I just discovered libnice. Detlev Casanova. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] GSoC Status
Hey folks, After being in a bug hunting period in my code, I am back adding parts of Jingle ! The first one is that I succeed sending and receieving RTP data for a Jingle session which has not been that easy as the documentation for this library is not easy to understand (I now know why I should comment my code :-) ) Also, the Jingle calls GUI can now have sessions added (that was the hardest part, the rest of the GUI should not be complicated. And when I say the hardest part, it was not so hard, it was just a copy-paste mistake which gave me a headache for 2 days...) Kopete will first be able to send a video file (using Jingle of course and using video via rtp). The video format will be theora and I will use that to make tests. In what concerns the sound part, I'll also start with a sound file. The reason I'll transfer files is that Phonon does not support inputs yet (No microphone and no video input even though Video input and video widget are coming). A big part that I still have to implement is ICE-UDP. That's what will take the biggest part of the remaining GSoC time. I could be a bit slower than before to code beginning tomorrow as I will start studying (yes, again) and I receive my new laptop this evening... Cheers, Detlev Casanova. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] GSoC : Status
Hi folks, I have now an almost full chain of classes to have somethig that works ! But it does not work yet... The chain is missing parts. I don't have ice-udp yet, I only have something that looks like a raw-udp implementation but this spec is only for testing (is there still people not behind a NAT ?) and is confusing so I modified a bit the way it works : as it should be tested only in a local network, there is no "received" informational message, the data is sent as soon as the session-initiate has been received. Also, the candidate that the responder will send to the initiator is not used yet so it will stream only in one direction. I'm using libortp and it must be 0.13.1 (maybe less but I don't know exactly which version and the code is based on 0.13.1). I added a CMake module to find the library but I do not test the version yet. Kopete will try to compile (but won't succeed) if a bad version of ortp is installed. The payloads which will be used are first Theora for Video streaming and Speex for audio streaming. I ceetainly will use libraries to encode and decode theora and speex data as I don't think Phonon will be able to do that (which I understand as it is not what Phonon is for). I should commit this evening the latest source code as it is still in a very buggy state and I did not try my latest implementation yet. Cheers, Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] GSoC : 6th week
Hello there, Don't worry, I'm still alive and I will even be back online on the 9th of July :-) I had 2 weeks off in France where I thought I would have an internet connection which turned out to be false... But I worked on the Iris library anyway and I have now brand new JT_JingleAction and JT_PushJingleAction tasks which are managed by a JingleSessionManager and a JingleSession class. Kopete has a JingleCallsManager class which will "play" with JingleSession's, a JingleSessionManager and later, Phonon and Solid for Audio and Video. I had a little talk with Phonon guys and neither audio input nor video input are implemented in Phonon yet. They say I will have to wait for KDE 4.2 or maybe even later. I might have to work with them after the Iris part. (did I already talk about that ?) Currently, Kopete is able to receive a session-initiate Jingle action and ask the user what contents he wants to accept (currently, content names are shown but that part will be improved later.) The session-terminate or session-remove action can be sent. I'm working on the negotiation before a session-accept action. I already had something but I ran into a[n impasse] so I had to rewrite that part from scratch. As I don't have an internet connection, I can't commit nowadays but I try to make daily backup so I don't lose too much data if another part of my laptop decides to stop working (currently, the sound card, the DVD drive and the monitor are dead :-( ) Detlev Casanova signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] GSoC Status
Hi, I'm still alive, don't worry. I'm really sorry to send you so few informations but as Windows is unable to detect an USB Mass Storage device and people are not able to make it work, I prefer to go back to work and I'll send pre-dated mails later. Just so you know, I had a little way back in development because I did not quite understood the jingle specification but I'm still working on the negotiation. Cheers, Detlev Casanova ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] GSoC 2008 : week 5 (or 6 ?)
Hi there ! I'm trying to get used to a french keyboard to send you this message as I broke my laptop screen (well, it kind of exploded...). All data is still there but I had to wait 3 days to find a replacement screen. The current status of the project is... I'd say good. I can now have some talking between two Kopete and it starts negotiating a content. the rest has still to be implemented but the structure is already there. I'll send more informations and news as soon as I get a way to communicate for less than 2 euros for 10 minutes on an internet connection. Cheers, Detlev Casanova. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] GSoC 2008 : week 4
So, last week was the last one to be so unproductive (for my GSoC project of course). I already started to implement the Iris Jingle tasks. It doesn't go as quick as I wanted but, that will get better. Here's how I'd like to implement Jingle : On the Kopete side, we have a JingleSessionManager which... manages all Jingle sessions. This manager will have a graphical interface or the chat window will get the events from it or both, that doesn't matter that much for now. It also will be the path between the media manager (what manages audio and video) so the 2 parts are totally managed separately. On the Iris side, the JingleSession will be a class which collects all needed informations and start a Jingle task to establish the session. A first information collector is the JingleContent class. As a content tag in Jingle can have lots of different behavior, this class gets all needed informations for one content type and make a QDomElement containing the content tag to give it to JingleSession and the Jingle task. Kopete will start, modify and/or terminate the session only with the JingleSession and shouldn't have to use instances of any Jingle task. That is for sending an initiation request. When an initiation request is received, the Jingle task negotiate and establish the session, then give a JingleSession instance to Kopete so it can be used to modify or terminate the Jingle session the same way it is done in the other direction. Anyway, some little things are not quite clear : * I don't want to use a Jingle Task in Kopete and let the Jingle session manage it itself when I send an initiation request but when I receive an initiation request, I have to use that Task in Kopete code (That Task is always present waiting for a jingle initiation request). Wouldn't it be better if both direction worked the same way ? A Task and a Jingle session for both directions ? * I think that creating a Payload class and a Transport Class, etc... would become too much. That's why, currently, the payload-type element must be directly added in the form of a QDomElement. I don't know if it is good or not. Cheers, Detlev Casanova. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] GSoC 2008 : week 3 (a bit late too)
Hey, here's the weekly status of my project ! Well, it's not evolving at all as the last exams are not the simpler ones... Only 2 left and I will be fully operational :-) Nothing moved on Iris side, I may have to write code for Iris which has already been written by an Iris developper but not comitted anywhere yet. I looked a bit into Solid and Phonon which have no support for the microphone yet (neither the KDE nor Qt Version -- KDE 4.1 will have Phonon 4.2 and Qt 4.4 has Phonon 4.1 but the microphone will only be supported in 4.3+ or even only in 4.4+). I may have to work with Phonon guys also to make this work more quickly (This proves what I said in my application : writing an instant messaging client needs to play with different domains :) ) I really begin working on that project on Friday morning. Yay ! Cheers, Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 163954] shortcut-paste in chatwindow inserts text twice
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=163954 detlev.casanova gmail com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Additional Comments From detlev.casanova gmail com 2008-06-13 10:56 --- *** This bug has been marked as a duplicate of 163535 *** ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] GSoC 2008 : week 2 (a bit late)
Hello there, I'm nearly finished with my exams, only 4 (maybe 5) left ! As I really don't have much to work on GSoC now with all the studying and stuff, I can say that there is not so much done yet. The Jingle implementation in Iris does not exists yet but Remko Tronçon has already implemented the negatioation part which is not yet in Iris svn. I still don't know if I will have the pleasure to work with the Psi/Iris team as they seems opposed to welcome other developpers within the Iris project for now ( http://lists.affinix.com/pipermail/delta-affinix.com/2008-June/001229.html ). So, things are getting placed but it's not as easy as I thought. Now, I'll just go back to study :-) . Best regards, Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 163329] Garbled account configuration window
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=163329 --- Additional Comments From detlev.casanova gmail com 2008-06-06 09:49 --- It seems that the widgets don't expand to their maximum vertical size. Is it better if you increase the size of the window ? ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 162918] browser is not configurable
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162918 --- Additional Comments From detlev.casanova gmail com 2008-05-30 22:27 --- The default browser is configured within KDE, you should tell KDE what browser to use by default. See here for details on How to change the default browser : http://kb.mozillazine.org/Setting_Your_Default_Browser#KDE ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 154059] cannot connect to gmail account
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=154059 detlev.casanova gmail com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Additional Comments From detlev.casanova gmail com 2008-05-28 12:05 --- This bug is solved in Kopete svn. If you do not want to use kopete svn, you'll have to wait for KDE 4.1. *** This bug has been marked as a duplicate of 154940 *** ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 162741] gtalk does not connect
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162741 detlev.casanova gmail com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Additional Comments From detlev.casanova gmail com 2008-05-28 12:02 --- *** This bug has been marked as a duplicate of 154940 *** ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 162550] wrong 'Save to' path when recieving files
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162550 --- Additional Comments From detlev.casanova gmail com 2008-05-25 00:50 --- Could you check in your kopete config file /home//.kde4/share/config/kopeterc if you have a defaultPath entry in the [File Transfer] section ? this default path should be the source of your problem, reset it to /home/ or simply remove the whole [File Transfer] entry as the path used in kopete is your home folder if the entry does not exist. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 154940] Cannot connect to GTalk using Kopete SVN
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=154940 detlev.casanova gmail com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From detlev.casanova gmail com 2008-05-23 09:50 --- *** Bug has been marked as fixed ***. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 154940] Cannot connect to GTalk using Kopete SVN
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=154940 --- Additional Comments From detlev.casanova gmail com 2008-05-20 17:15 --- The problem seemed to be a certificate problem, I committed a patch wich should solve the problem, please try the latest svn revision. That seems weird iris behaved like that, proposing SSL version 1 to the server. But the problem was actually on the Kopete side :) ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 162316] kopete crashes when I click on video in config dialog
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=162316 --- Additional Comments From detlev.casanova gmail com 2008-05-19 18:35 --- If you succeed reproducing it, could you also post what is written in the console (when you run kopete from a console) ? You will have to compile kopete in full debug mode (Use flag "debug" for gentoo) if not already done. What version of Qt are you using ? ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 154940] Cannot connect to GTalk using Kopete SVN
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=154940 --- Additional Comments From detlev.casanova gmail com 2008-05-16 10:45 --- Created an attachment (id=24789) --> (http://bugs.kde.org/attachment.cgi?id=24789&action=view) Wireshark Log when psi tries to connect to talk.google.com ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 154940] Cannot connect to GTalk using Kopete SVN
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=154940 --- Additional Comments From detlev.casanova gmail com 2008-05-16 10:41 --- Created an attachment (id=24787) --> (http://bugs.kde.org/attachment.cgi?id=24787&action=view) Wireshark Log when kopete tries to connect to talk.google.com ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 154940] Cannot connect to GTalk using Kopete SVN
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=154940 --- Additional Comments From detlev.casanova gmail com 2008-05-16 10:38 --- I have the same probleme with kopete, It seems to be a problem with QCA and Qt because I had the same problem using a QSslSocket in an other project. It seems that in Psi, using wireshark, Psi sends its SSLv2 "Client hello" using that secure socket layer : "SSLv2 Record Layer: Client Hello". But Kopete sends its "Client hello" using the "SSL Record Layer: Handshake Protocol: Client Hello" secure socket layer which talk.google.com does not seem to understand as it closes the connection 20 seconds later. I attached all informations from wireshark as I don't have enough knowledge in that area to find the problem, maybe someone does know that. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 145307] multi-line messages using jabber show up as 1 line
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=145307 --- Additional Comments From detlev.casanova gmail com 2008-05-16 09:49 --- SVN commit 808260 by casanova: BUG: 145307 CCBUG: 145307 * Keeps end of line in message part when sending a message which contains several lines. M +1 -1 kopetemessage.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=808260 ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [patch] End of line not shown
Hello, Here's a patch correcting the problem of end of line not shown in the message part when sending a message wich contains several lines. The KRichTextEditPart::text() method returns the text in paragraphs instead of putting at the end of lines when it is asked to return rich text. When the message was escaped ( Message::escapedBody() ) , all and tags were removed, that's why the text was wrongly shown in the message part (plain text is send to the contact so no problem there). I simply removed the suppression of these paragraphs so it is shown right in the message part. Another solution would be to remove the open tag () and replace the close tag () by a new line tag () so it is *really* escaped. It works now with paragraphs so... "If it's not broken, don't fix it" :p -- Detlev Casanova Student at the Université de Liège (computer science) Google Summer of Code 2008 student. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Popup notifications
On Thursday 01 May 2008 14:38:48 Michal Svec wrote: > > I wrote this little patch which shows the popup only when the window > > is not already opened. > > But i still want the popup when the window is open but has not the > focus. (so i click the popup to see the message) > >>> > >>> Well, each one has its preferences, I don't find it very usable. > >>> That should be configurable then. > >>> You want to have notifications of all messages or only 1 notifications > >>> for all messages that comes while the window has no focus ? > >> > >> For example it makes sense when you have the chat window open on one > >> desktop while working on another. > > > > Yeah, I got that :) > > What I don't get is why the text of the popup should be saved in a file > > if the popup is not shown. > > That sounds indeed strange :) > > >> I'd actually like to go even further, it would be good to have some > >> kind of a permanent notifier (like animated tray icon) when I have > >> a new message, until I actually read it. > > > > It's already the case, when a message is received, the Kopete icon in > > the system tray gets animated. You even can click it to see the message. > > You're right, I've seen it somewhere. But it certainly does not work for > me (0.12.6), any hints where to look? Version 0.12.6 of Kopete is for KDE 3, I'm talking here of Kopete 0.50.50 in KDE 4 :-) however, it seems to get animated in Kopete 0.12.7 too but only if the chat window is not opened. Detlev signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Messagerie instantanée
On Wednesday 30 April 2008 21:47:42 Matt Rogers wrote: > On Wednesday 30 April 2008 13:35:58 Detlev Casanova wrote: > > Please post on KDE mailing-lists in english. > > If you're going to answer, then you should translate the original message > for those of us that don't speak the different language. I hesitated :) > > On Wednesday 30 April 2008 18:22:57 Guy Jeanniard wrote: > > > Bonjour, > > > Je viens d'installer Mandriva Linux avec Kopete pour la messagerie > > > instantanée. Je ne trouve pas de réponse aux questions suivantes: Hi, I just installed Mandriva Linux with kopete for instant messaging. I have no answer for those question : > > > * comment envoyer un message en différé (c'est à dire à une personne > > > non connectée qui trouvera ce message lorsqu'elle se connectera)? * How can I send a message to an offline contact so he can read it when he connects ? > > That's not supported in Kopete for KDE 3.5 > > > > > * comment effacer l'historique des dialogues? * How can I clear the history of my messages ? > > Good question :) > > > > > * comment transférer mon dossier de partage de MSN / Windows Vista chez > > > Kopete? Merci d'avance de votre assistance. How can I transfer my shared folder from MSN/Windows Vista to Kopete(/Linux) ? Thanks for your help. > > That's not supported yet in Kopete. > > > > Don't forget that Windows Live Messenger protocol is not opened and not > > documented. That's why every features of this protocol is not supported > > in free software. > > > > Detlev. > > ___ > kopete-devel mailing list > kopete-devel@kde.org > https://mail.kde.org/mailman/listinfo/kopete-devel -- Detlev Casanova Student at the Université de Liège (computer science) Open source project : Kapture ( http://kapture.berlios.de/ ) Google Summer of Code 2008 student. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Messagerie instantanée
Please post on KDE mailing-lists in english. On Wednesday 30 April 2008 18:22:57 Guy Jeanniard wrote: > Bonjour, > Je viens d'installer Mandriva Linux avec Kopete pour la messagerie > instantanée. Je ne trouve pas de réponse aux questions suivantes: > * comment envoyer un message en différé (c'est à dire à une personne non > connectée qui trouvera ce message lorsqu'elle se connectera)? That's not supported in Kopete for KDE 3.5 > * comment effacer l'historique des dialogues? Good question :) > * comment transférer mon dossier de partage de MSN / Windows Vista chez > Kopete? Merci d'avance de votre assistance. That's not supported yet in Kopete. Don't forget that Windows Live Messenger protocol is not opened and not documented. That's why every features of this protocol is not supported in free software. Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Popup notifications
On Wednesday 30 April 2008 12:17:53 Michal Svec wrote: > On Wed, 23 Apr 2008, Detlev Casanova wrote: > >>> I wrote this little patch which shows the popup only when the window is > >>> not already opened. > >> > >> But i still want the popup when the window is open but has not the > >> focus. (so i click the popup to see the message) > > > > Well, each one has its preferences, I don't find it very usable. > > That should be configurable then. > > You want to have notifications of all messages or only 1 notifications > > for all messages that comes while the window has no focus ? > > For example it makes sense when you have the chat window open on one > desktop while working on another. Yeah, I got that :) What I don't get is why the text of the popup should be saved in a file if the popup is not shown. > I'd actually like to go even further, it would be good to have some > kind of a permanent notifier (like animated tray icon) when I have > a new message, until I actually read it. It's already the case, when a message is received, the Kopete icon in the system tray gets animated. You even can click it to see the message. Detlev. signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Bug 112213 (XMPP STARTTLS)
On Tuesday 29 April 2008 17:42:47 Matt Rogers wrote: > On Tuesday 29 April 2008 10:35:37 Peter Saint-Andre wrote: > > Recently we've had some troubles with support for the legacy SSL port > > (5223) at the jabber.org XMPP service. This has exposed the fact that > > some IM clients (including Kopete) do not yet support the STARTTLS > > feature (upgrade of port 5222 to an encrypted connection) first defined > > in RFC 3920 (published in October 2004). As author of RFC 3920, I would > > be happy to answer any questions about STARTTLS or to connect the Kopete > > team with other XMPP developers so that we can fix this bug. > > > > Thanks! > > > > Peter > > Does PSI support this already? We're using their jabber client code. > Perhaps we need to sync with their latest and greatest stuff if they > already support this Yes, Psi supports STARTTLS. Well, at least, Iris does. It even support both old and new "STARTTLS" variations. Kopete seems to use libiris from psi svn at version 356 (that seems old but that is what the README_BEFORE_COMMITTING file says), they are now at version 1131. However, when the jabber.org server had problems with the 5223 port, Psi did not want to connect (but I'm using 0.10 so... it's also quite old) I think that an update of libiris would be a good thing but I don't know if this will still be API compatible. -- Detlev Casanova Student at the Université de Liège (computer science) Open source project : Kapture ( http://kapture.berlios.de/ ) Google Summer of Code 2008 student (Kopete Jingle). signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Popup notifications
On Wednesday 23 April 2008 01:01:20 Olivier Goffart wrote: > Le mercredi 23 avril 2008, Detlev Casanova a écrit : > > On Tuesday 22 April 2008 23:53:42 Olivier Goffart wrote: > > > Le mardi 22 avril 2008, Detlev Casanova a écrit : > > > > Hi there, > > > > I found annoying the fact that every time you receive a message, > > > > kopete shows a popup asking if you want to see it or ignore it even > > > > if the chat window is already opened and already has focus. > > > > > > Right > > > > > > > I wrote this little patch which shows the popup only when the window > > > > is not already opened. > > > > > > But i still want the popup when the window is open but has not the > > > focus. (so i click the popup to see the message) > > > > Well, each one has its preferences, I don't find it very usable. > > That should be configurable then. > > You want to have notifications of all messages or only 1 notifications > > for all messages that comes while the window has no focus ? > > > > > > That patch is made for the svn trunk revision 799857 of kdenetwork. > > > > It modifies kopete/kopete/kopete.notifyrc to have a new Event > > > > (kopete_popup_contact_incoming) which shows a popup while the old one > > > > (kopete_contact_incoming) doesn't anymore and > > > > kopete/libkopete/private/kopeteviewmanager.cpp to use the right > > > > notify Event. > > > > > > Why do you remove the text and the contextes and the action in that > > > case for the different notification? > > > > For the text and the actions, as the popup won't be shown, it's not > > usefull, for contextes, it's my mistake :) > > The text may be logged to a file. And the popup may still apears if the > user configure it. Here's the corrected patch, text, actions and contextes are now left behind. -- Detlev Casanova Student at the Université de Liège (computer science) Open source project : Kapture ( http://kapture.berlios.de/ ) Index: kopete/kopete/kopete.notifyrc === --- kopete/kopete/kopete.notifyrc (revision 800342) +++ kopete/kopete/kopete.notifyrc (working copy) @@ -334,6 +334,95 @@ Comment[zh_TW]=ن�ن�م�هو�ن� Contexts=contact,group,class Sound=KDE-Im-Message-In.ogg +Action=Sound|Taskbar +Persistant=true + +[Event/kopete_popup_contact_incoming] +Name=Incoming Message With Popup +Name[ca]=Missatge entrant +Name[cs]=Pإأchozأ zprأ�va +Name[da]=Indkommende besked +Name[de]=Eingehende Nachricht +Name[el]=خخ�دخ�دددخ�خ�خ�خ؟ خ�خ�خ�د خ�خ� +Name[eo]=Alvenanta mesaؤo +Name[es]=Mensaje entrante +Name[et]=Sisenev sأ�num +Name[fi]=Saapuvat viestit +Name[fr]=Message entrant +Name[ga]=Teachtaireacht Isteach +Name[gl]=Mensaxe entrante +Name[hi]=ـ¤ـ¤�ـ¤ ـ¤�ـ¤ـ¤�ـ�ـ¤� +Name[it]=Messaggio in arrivo +Name[ja]=مل؟�ك�كك؛ك�ك� +Name[km]=فف�فقففقففف +Name[ko]=ً�ٌٌ� ٌٌ +Name[lt]=Gauta إ�inutؤ +Name[lv]=Ienؤkusi ziإa +Name[nb]=Innkommende melding +Name[nds]=Ankamen Naricht +Name[nl]=Inkomend bericht +Name[pa]=ـ� ـ��ـ�؟ـ��ـ�� ـ��ـ�ـ��ـ�ـ��ـ�� +Name[pl]=Wiadomoإؤ przychodzؤ ca +Name[pt]=Mensagem Recebida +Name[pt_BR]=Mensagem Recebida +Name[ru]=ذر ذ�ذ�ررذ�ذ� رذ�ذ�ذ�رذ�ذ�ذ�ذ� +Name[sl]=Prihajajoؤe sporoؤilo +Name[sv]=Inkommande meddelande +Name[tr]=Gelen ؤ�letiler +Name[uk]=ذر رذ�ذ�ذ� ذ؟ذ�ذ�رذ�ذ�ذ�ذ؛ذ�ذ�ذ�ر +Name[x-test]=xxIncoming Messagexx +Name[zh_CN]=ن�م�هن�ن� +Name[zh_TW]=ى�ل�هو�ن� +Comment=An incoming message has been received and a popup has to be shown +Comment[bn]=ـ�ـ�ـ�ـ�؟ ـ� ـ��ـ�ـ�¤ـ��ـ�ـ��ـ�ـ�ـ� ـ�،ـ��ـ��ـ�ـ�¤ـ�� ـ�ـ�ـ��ـ��ـ�� ـ�ـ��ـ�� ـ��ـ�ـ�ـ�ـ� +Comment[ca]=S'ha rebut un missatge entrant +Comment[cs]=Byla obdrإ�ena pإأchozأ zprأ�va +Comment[da]=En indkommende besked er blevet modtaget +Comment[de]=Eine eingehende Nachricht wurde empfangen +Comment[el]=خدخ�خ� خ؛خ�دخ�خ�خ� خخ�خ� خ�خ�دخ�دددخ�خ�خ�خ؟ خ�خ�خ�د خ�خ� +Comment[eo]=Alvenanta mesaؤo estis ricevita +Comment[es]=Se ha recibido un mensaje entrante +Comment[et]=Saabus sأ�num +Comment[eu]=Sarrerako mezu bat jaso da +Comment[fi]=Viesti on saapunut +Comment[fr]=Un message entrant a أ�tأ� reأ�u +Comment[ga]=Fuarthas teachtaireacht isteach +Comment[gl]=Recebeuse unha mensaxe entrante +Comment[he]=طط�ط�طط طط�ط� ط طط ط� +Comment[hi]=ـ¤ـ¤ ـ¤ـ¤�ـ¤ ـ¤�ـ¤ـ¤�ـ�ـ¤� ـ¤�ـ�ـ¤�ـ¤�ـ¤�ـ�ـ¤¤ ـ¤�ـ�ـ¤ +Comment[hr]=Primljena je dolazna poruka +Comment[hu]=Bejأ�vإ أ�zenet أ�rkezett +Comment[is]=Skeyti mأ�ttekiأ� +Comment[it]=أ stato ricevuto un nuovo messaggio +Comment[ja]=مل؟�ك�كك؛ك�ك�كم�كك�كك +Comment[km]=فف�فقففف�فقفففف؛فففقفف�فقف ف�ف +
Re: [kopete-devel] Popup notifications
On Wednesday 23 April 2008 01:01:20 Olivier Goffart wrote: > Le mercredi 23 avril 2008, Detlev Casanova a écrit : > > On Tuesday 22 April 2008 23:53:42 Olivier Goffart wrote: > > > Le mardi 22 avril 2008, Detlev Casanova a écrit : > > > > Hi there, > > > > I found annoying the fact that every time you receive a message, > > > > kopete shows a popup asking if you want to see it or ignore it even > > > > if the chat window is already opened and already has focus. > > > > > > Right > > > > > > > I wrote this little patch which shows the popup only when the window > > > > is not already opened. > > > > > > But i still want the popup when the window is open but has not the > > > focus. (so i click the popup to see the message) > > > > Well, each one has its preferences, I don't find it very usable. > > That should be configurable then. > > You want to have notifications of all messages or only 1 notifications > > for all messages that comes while the window has no focus ? > > > > > > That patch is made for the svn trunk revision 799857 of kdenetwork. > > > > It modifies kopete/kopete/kopete.notifyrc to have a new Event > > > > (kopete_popup_contact_incoming) which shows a popup while the old one > > > > (kopete_contact_incoming) doesn't anymore and > > > > kopete/libkopete/private/kopeteviewmanager.cpp to use the right > > > > notify Event. > > > > > > Why do you remove the text and the contextes and the action in that > > > case for the different notification? > > > > For the text and the actions, as the popup won't be shown, it's not > > usefull, for contextes, it's my mistake :) > > The text may be logged to a file. Why should the text be logged to a file ? To re-read it later ? But why ? The history is there for that and the message will be shown in the chat window anyway. I think I'm missing something... > And the popup may still apears if the > user configure it. Right. -- Detlev Casanova Student at the Université de Liège (computer science) signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Popup notifications
On Tuesday 22 April 2008 23:53:42 Olivier Goffart wrote: > Le mardi 22 avril 2008, Detlev Casanova a écrit : > > Hi there, > > I found annoying the fact that every time you receive a message, kopete > > shows a popup asking if you want to see it or ignore it even if the chat > > window is already opened and already has focus. > > Right > > > I wrote this little patch which shows the popup only when the window is > > not already opened. > > But i still want the popup when the window is open but has not the focus. > (so i click the popup to see the message) Well, each one has its preferences, I don't find it very usable. That should be configurable then. You want to have notifications of all messages or only 1 notifications for all messages that comes while the window has no focus ? > > That patch is made for the svn trunk revision 799857 of kdenetwork. > > It modifies kopete/kopete/kopete.notifyrc to have a new Event > > (kopete_popup_contact_incoming) which shows a popup while the old one > > (kopete_contact_incoming) doesn't anymore and > > kopete/libkopete/private/kopeteviewmanager.cpp to use the right notify > > Event. > > Why do you remove the text and the contextes and the action in that case > for the different notification? For the text and the actions, as the popup won't be shown, it's not usefull, for contextes, it's my mistake :) -- Detlev Casanova Student at the Université de Liège (computer science) Open source project : Kapture ( http://kapture.berlios.de/ ) signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] Popup notifications
Hi there, I found annoying the fact that every time you receive a message, kopete shows a popup asking if you want to see it or ignore it even if the chat window is already opened and already has focus. I wrote this little patch which shows the popup only when the window is not already opened. That patch is made for the svn trunk revision 799857 of kdenetwork. It modifies kopete/kopete/kopete.notifyrc to have a new Event (kopete_popup_contact_incoming) which shows a popup while the old one (kopete_contact_incoming) doesn't anymore and kopete/libkopete/private/kopeteviewmanager.cpp to use the right notify Event. Let me know. Cheers. -- Detlev Casanova Student at the Université de Liège (computer science) Open source project : Kapture ( http://kapture.berlios.de/ ) Index: kopete/kopete/kopete.notifyrc === --- kopete/kopete/kopete.notifyrc (revision 799857) +++ kopete/kopete/kopete.notifyrc (working copy) @@ -334,6 +334,95 @@ Comment[zh_TW]=æ¥æ¶å°çè¨æ¯ Contexts=contact,group,class Sound=KDE-Im-Message-In.ogg +Action=Sound|Taskbar +Persistant=true + +[Event/kopete_popup_contact_incoming] +Name=Incoming Message With Popup +Name[ca]=Missatge entrant +Name[cs]=PÅÃchozà zpráva +Name[da]=Indkommende besked +Name[de]=Eingehende Nachricht +Name[el]=ÎιÏεÏÏÏμενο Î¼Î®Î½Ï Î¼Î± +Name[eo]=Alvenanta mesaÄo +Name[es]=Mensaje entrante +Name[et]=Sisenev sõnum +Name[fi]=Saapuvat viestit +Name[fr]=Message entrant +Name[ga]=Teachtaireacht Isteach +Name[gl]=Mensaxe entrante +Name[hi]=à¤à¤µà¤ सà¤à¤¦à¥à¤¶ +Name[it]=Messaggio in arrivo +Name[ja]=åä¿¡ã¡ãã»ã¼ã¸ +Name[km]=áá¶áâááâááá +Name[ko]=ë©ìì§ ìì +Name[lt]=Gauta žinutÄ +Name[lv]=IenÄkusi ziÅa +Name[nb]=Innkommende melding +Name[nds]=Ankamen Naricht +Name[nl]=Inkomend bericht +Name[pa]=ਠਰਿਹਾ ਸà©à¨¨à©à¨¹à¨¾ +Name[pl]=WiadomoÅÄ przychodzÄ ca +Name[pt]=Mensagem Recebida +Name[pt_BR]=Mensagem Recebida +Name[ru]=ÐÑ Ð¾Ð´ÑÑее ÑообÑение +Name[sl]=PrihajajoÄe sporoÄilo +Name[sv]=Inkommande meddelande +Name[tr]=Gelen Ä°letiler +Name[uk]=ÐÑ Ñдне повÑÐ´Ð¾Ð¼Ð»ÐµÐ½Ð½Ñ +Name[x-test]=xxIncoming Messagexx +Name[zh_CN]=æ¶å°çæ¶æ¯ +Name[zh_TW]=é²ä¾çè¨æ¯ +Comment=An incoming message has been received and a popup has to be shown +Comment[bn]=à¦à¦à¦à¦¿ ঠনà§à¦¤à¦°à§à¦®à§à¦à§ বারà§à¦¤à¦¾ à¦à§à¦°à¦¹à¦£ à¦à¦°à¦¾ হà§à§à¦à§ +Comment[ca]=S'ha rebut un missatge entrant +Comment[cs]=Byla obdržena pÅÃchozà zpráva +Comment[da]=En indkommende besked er blevet modtaget +Comment[de]=Eine eingehende Nachricht wurde empfangen +Comment[el]=ÎÏει ληÏθεί Îνα ειÏεÏÏÏμενο Î¼Î®Î½Ï Î¼Î± +Comment[eo]=Alvenanta mesaÄo estis ricevita +Comment[es]=Se ha recibido un mensaje entrante +Comment[et]=Saabus sõnum +Comment[eu]=Sarrerako mezu bat jaso da +Comment[fi]=Viesti on saapunut +Comment[fr]=Un message entrant a été reçu +Comment[ga]=Fuarthas teachtaireacht isteach +Comment[gl]=Recebeuse unha mensaxe entrante +Comment[he]=×תק×× ×סר × ×× ×¡ +Comment[hi]=à¤à¤ à¤à¤µà¤ सà¤à¤¦à¥à¤¶ पà¥à¤°à¤¾à¤ªà¥à¤¤ हà¥à¤ +Comment[hr]=Primljena je dolazna poruka +Comment[hu]=BejövŠüzenet érkezett +Comment[is]=Skeyti móttekið +Comment[it]=à stato ricevuto un nuovo messaggio +Comment[ja]=åä¿¡ã¡ãã»ã¼ã¸ãå±ãã¾ãã +Comment[km]=áá¶áâááá½áâáááá»áááâáá½áâá á¼á +Comment[ko]=ë¤ì´ì¤ë ë©ìì§ë¥¼ ë°ì +Comment[lt]=Gauta nauja žinutÄ +Comment[lv]=Ir saÅemta ienÄkoÅ¡Ä ziÅa +Comment[mk]=ÐÑимена е доÑдовна поÑака +Comment[nb]=En innkommende melding er mottatt +Comment[nds]=En Naricht keem rin +Comment[nl]=Er is een inkomend bericht ontvangen +Comment[pl]=NadeszÅa nowa wiadomoÅÄ +Comment[pt]=Foi recebida uma mensagem +Comment[pt_BR]=chegou nova mensagem +Comment[ru]=ÐолÑÑено новое ÑообÑение +Comment[sk]=PrÃchod správy +Comment[sl]=Prejeto je bilo prihajajoÄe sporoÄilo +Comment[sr]=Primljena je dolazeÄa poruka [EMAIL PROTECTED] je dolazeÄa poruka +Comment[sv]=Ett inkommande meddelande har anlänt +Comment[ta]=à®à®³à¯à®µà®°à¯à®®à¯ தà®à®µà®²à¯ பà¯à®±à®ªà¯à®ªà®à¯à®à®¤à¯ +Comment[tg]=ÐайÑми воÑидÑаванда ÒабÑл гаÑдид +Comment[tr]=Bir gelen mesaj alındı +Comment[uk]=ÐÑÑимано Ð²Ñ Ñдне повÑÐ´Ð¾Ð¼Ð»ÐµÐ½Ð½Ñ +Comment[uz]=Ð¥Ð°Ð±Ð°Ñ ÒабÑл Òилинди +Comment[x-test]=xxAn incoming message has been receivedxx +Comment[zh_CN]=æ¶å°äºä¸æ¡æ¶æ¯ +Comment[zh_HK]=æ¶å°æ°è¨æ¯ +Comment[zh_TW]=æ¥æ¶å°çè¨æ¯ +Contexts=contact,group,class +Sound=KDE-Im-Message-In.ogg Action=Sound|Popup|Taskbar Persistant=true Index: kopete/libkopete/private/kopeteviewmanager.cpp === --- kopete/libkopete/private/kopeteviewmanager.cpp
[kopete-devel] GSoC : Jingle Video and Audio support for Kopete
Hi all ! I have been selected to add support for Jingle Video and Audio in Kopete as a Google Summer of Code student. * About me : I am a 19 years old student from Belgium. I study at the University of Liège in computer science section and I am in my first year. I have backgrounds in Jabber client, C++ and Qt 4 programming as I started, 1 year ago, a project which is a Qt4 based Xmpp client. * About the project : The title say it all, I will add support for Jingle Video and Jingle Audio in Kopete as the most of jabber clients are missing this feature currently and Kopete is part of it. As I am already familiar with Jingle and the Xmpp protocol, I am the best student for this project :) For the end of the summer, I expect to implement Jingle and make it work for the most of people (especially people behind a NAT who might have more troubles... ) Olivier Goffart will be my Mentor, that will make it easy for both of us as we both have French as first language. I attached the whole application of the project for curious people ;) Well, let's go then :) -- Detlev Casanova Student at the Université de Liège (computer science) Open source project : Kapture ( http://kapture.berlios.de/ ) application-kopete Description: Binary data signature.asc Description: This is a digitally signed message part. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] error while starting webcam (MSN)
Hello !
* When so want to show me his webcam, I get this error :
(Stripped binary data)
kopete (msn): [void P2P::TransferContext::acknowledge(const P2P::Message&)]
0x8754958
kopete (msn - raw protocol): [virtual void P2P::Webcam::processMessage(const
P2P::Message&)] Message contents:
ReflData:72753D687474703A2F2F6D307265666C6563746F7232392E73706F746C6966652E6E65743A393030302674693D35373436393032363334313933363737333939
kopete (msn - raw protocol):
kopete (msn): [void P2P::TransferContext::error()]
kopete (msn): [void P2P::TransferContext::sendMessage(P2P::Message&, const
QByteArray&)] MSNSLP/1.0 500 Internal Error
To:
From:
Via: MSNSLP/1.0/TLP ;branch={3C5B157A-8C42-1E68-30E0-B667363A5AE0}
CSeq: 1
Call-ID: {8A95D664-E9B6-478F-9755-A14D6986F08A}
Max-Forwards: 0
Content-Type: null
Content-Length: 1
* If I want to send my webcam image, I get this error after a while :
(Stripped binary data)
kopete (msn): [void P2P::TransferContext::acknowledge(const P2P::Message&)]
0x8754958
kopete (msn - raw protocol): [virtual void P2P::Webcam::processMessage(const
P2P::Message&)] received, BYE MSNMSGR:[EMAIL PROTECTED] MSNSLP/1.0
To:
From:
Via: MSNSLP/1.0/TLP ;branch={E145F316-0542-4017-B323-717DCBCDA9C9}
CSeq: 0
Call-ID: {361797D2-AF81-60F1-625A-8E5D62E775CB}
Max-Forwards: 0
Content-Type: application/x-msnmsgr-sessionclosebody
Content-Length: 22
Context: dAMAgQ==
kopete (msn - raw protocol):
kopete (msn): [virtual P2P::Webcam::~Webcam()]
###E#N#D
* I didn't have this problem before I had to reset my router's param's...
Any Idea ?
Thanks.
Detlev.
pgpXRzcgrp5fF.pgp
Description: PGP signature
___
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
