Re: Kopete to boil it's own soup? Why?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Kopete to boil it's own soup? Why?
by Jason Keirstead on Tuesday 06/Jan/2004, @04:44

If libyahoo is feature complete, then porting it to the KDE codebase will result in all those features still being supported, along with the benefits of KDE like KIO support for file transfers, better memory management through QObjects, etc.

Really, maintaining links to these external C libraries in Kopete has never been anything but a pain in the ass. The code is horrible to maintain because it is all C based, there's constant memory problems, getting things updated in the main tree is often a pain, and you've got all this duplicated/obsoltee code everywhere because algorithms are already present elsewhere in QT or KDELibs. Couple this with the fact that you can't integrate the KDE code into the library because then you lose the ability to update it when new versions come out, and you've got a big mess.

Thats why we have our own homegrown support for all protocols now except Yahoo and SMS. It's just not worth the effort to use the other code.

Related Links

·   Articles on Developer
·   Also by Jason Keirstead
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )


		"I tried to play with some toy applications and enjoyed it." -- Werner Trobin
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.