USENIX Association Proceedings of the FREENIX Track: 2004 USENIX Annual Technical Conference Boston, MA, USA June 27–July 2, 2004 © 2004 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email:
[email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. KDE Kontact: An Application Integration Framework PIM Components Get Together David Faure Ingo Klock¨ er Tobias Konig¨ Daniel Molkentin KDE Project KDE Project KDE Project KDE Project
[email protected] [email protected] [email protected] [email protected] Zack Rusin Don Sanders Cornelius Schumacher KDE Project KDE Project KDE Project
[email protected] [email protected] [email protected] Abstract Kontact (section 4). It will discuss the importance of open standards (section 5), give an insight into Kontact Kontact is the new integrated KDE personal informa- as project (section 6) and will conclude with informa- tion management application. Well, it seems new, but tion about the availability of Kontact (section 7), final in fact only the shiny surface is new. Under the hood remarks (section 8) and some information about the au- well-known time-honored KDE applications like KMail, thors of Kontact (section 9). KOrganizer, KAddressBook, KNotes and KNode do their work. This paper describes how KDE component 2 Components vs. Monolithism technologies like KParts, DCOP or XMLGUI enable Why bother with integrating originally disparate appli- embedding of applications to create something which is cations? Why not build a monolithic integrated appli- more than the sum of the parts.