Madman,
Neither one. Kopete shows my Yahoo account as "Connecting." I tried using both miguelito_fierro and miguelito_fierro@yahoo.com. Same behavior either way.

I am chatting via XMPP with a friend who also has a Yahoo account. She doesn't see me online on Yahoo, and I don't see her.

The other protocols I use (AIM, MSN, XMPP) all seem to work fine. Which is what we expect too, I think.

Oh! I see it now. Yeah. Sorry, my bad. It's not working.

@cwizard: Kopete does have that infrastructure. It is simply that the plugins are written in C++ and are therefore not directly distributable to users. Therefore the fix can only be made when an official KDE release is made, or unless distributions back port the fix.

One quick question: can't the Pidgin code for Yahoo connectivity be borrowed? Both Pidgin and Kopete are GPL, aren't they? If so, why not use what the Pidgin team has already done?

Kopete in trunk may have already been fixed. Due to the invasiveness of the change it probably will not be possible to backport this to the KDE 4.3 branch however. This means that only KDE Trunk users have a Kopete which works with Yahoo, once it is fixed.

biffster wrote:One quick question: can't the Pidgin code for Yahoo connectivity be borrowed? Both Pidgin and Kopete are GPL, aren't they? If so, why not use what the Pidgin team has already done?

I did borrow it. I took their patch and adapted it to our code. I borrowed several changes, in fact. Now, I have no problems connecting or being shown as online to other clients. In short, rather than endlessly discussing this or that about how Kopete should be coded, written, designed, etc., how about you post some concrete information on the bugs that exist for the "yahoo still doesn't connect" problem? I can't fix it if I can't reproduce it and I can't fix it if I don't have the data that shows the problem (in lieu of being able to reproduce the issue)

bcooksley wrote:Kopete in trunk may have already been fixed. Due to the invasiveness of the change it probably will not be possible to backport this to the KDE 4.3 branch however. This means that only KDE Trunk users have a Kopete which works with Yahoo, once it is fixed.

The same fix is in trunk, the 4.3 branch, and the 4.2 branch. There have been no additional changes to fix other bugs, because I can't reproduce anything or I lack data to make an educated decision about something that's wrong.

bcooksley wrote:Kopete in trunk may have already been fixed. Due to the invasiveness of the change it probably will not be possible to backport this to the KDE 4.3 branch however. This means that only KDE Trunk users have a Kopete which works with Yahoo, once it is fixed.

"In truck"?
Could you please translate that into English?
Thanks.

bcooksley wrote:@cwizard: Kopete does have that infrastructure. It is simply that the plugins are written in C++ and are therefore not directly distributable to users. Therefore the fix can only be made when an official KDE release is made, or unless distributions back port the fix.

Thanks for taking the time to reply, but since I don't write code I don't have the first clue as to why the plug-ins are not distributable to the users or why they couldn't be written in manner that would make them distributable. If you have the time to explain that I would appreciate it, but if not, no problem.

Trunk is the development branch of KDE. In this case KDE 4.4. It is not recommended for use by users as it contains newer features which have not yet fully been developed, leading to crashes, incorrect activity, data loss, etc.

Plugins are not distributable because they are written in C++. C++ is a compiled language which requires the installation of a development environment in order to be turned into executables usable by the computer. Distributions compile the KDE source code, and package the executables which users then install. As a result, fixes are usually only distributed when it severely affects a distributions users, or when a KDE Bugfix 0.0.x release is made.

In other words, these plugins for kopete are compile-time pluggable rather than run-time pluggable, so you can't just download the upgraded kopete yahoo IM plugin and go, you have to upgrade kopete itself; which, since kopete is integrated so nicely into the rest of KDE and generally packaged and released together with the rest of KDE, means that in order to get the updated yahoo IM plugin for kopete you have to wait for the next release of KDE to hit your distribution.

One question that brings up is: will this update be backported for KDE 4.3.2 (which I assume is due in the next week or so), or are we going to have to wait for KDE 4.4 (not due for another couple of months)?

bcooksley wrote:....Plugins are not distributable because they are written in C++. C++ is a compiled language which requires the installation of a development environment in order to be turned into executables usable by the computer. Distributions compile the KDE source code, and package the executables which users then install. As a result, fixes are usually only distributed when it severely affects a distributions users, or when a KDE Bugfix 0.0.x release is made.

Thank you for taking the time to reply. While I don't write code I can run "make." Is the source code made available?

The source code is available.

Use the following command will download the latest code

Code: Select all

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdenetwork/

And the following will build it

Code: Select all

cd kdenetwork
mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$(kde4-config --prefix)
cd kopete
make

And this will install it

Code: Select all

sudo make install
kbuildsycoca4 --noincremental

Thank you very much!

Nope! Kicker and KDesktop are just as usable as it is before even though codes riddled with bugs. There are many ways to enhance its features for these components to simply fix bugs.