Source Compatability and DCOP

Don Sanders sanders at
Thu Aug 8 05:36:45 BST 2002

On Thursday 08 August 2002 06:31, Cornelius Schumacher wrote:
> On Wednesday 07 August 2002 19:15, Waldo Bastian wrote:
> > On Wednesday 07 August 2002 07:40 am, Ian Reinhart Geiser wrote:
> > > 	I noticed KAddressbook changed its dcop interface in a Source
> > > Incompatible manner.  This i guess broke KPilot, but worse it
> > > seems to have broken a few scripts I had done for a client for
> > > adding information to their addressbook from my TWIG web mail
> > > interface.
> > >
> > > 	Is there a policy on breaking DCOP interfaces on sub releases?
> >
> > DCOP interfaces are part of the API and MUST remain compatible.
> I don't think this is true in this case. The KAddressbook DCOP
> interface header file isn't installed to the system and it uses
> private classes of KAddressbook. This can't be part of the API we
> have to be compatible to.

Cornelius is correct, this DCOP interface is not part of an API that 
we should remain compatible with.

The KAddressbook DCOP interface was a private, temporary API for 
interoperability between KPilot and KAddressbook. This DCOP interface 
exposed temporary internal classes of KAddressBook, these classes 
were intended to be replaced once a new KDE address book library was 
implemented. Now the new KDE address book library is operational, the 
obsolete KAddressBook classes removed and the DCOP interface 

It's unfortunate that applications outside of KPilot have relied on 
this DCOP interface.

IIRC the KAddressBook DCOP interface was commented as being for the 
use of KPilot.


More information about the kde-core-devel mailing list