On Sunday 28 October 2001 06:58 pm, Mark Westcott wrote:
> I hope someone can help me.  KAdressbook has the DCOP call 'void
> changeEntry(QString key,ContactEntry changeEntry)', which I wish to call
> from some functionality I'm adding to KOrganizer.  However, the class
> ContactEntry is only defined within the addressbook sources, which are part
> of kdebase. Therefore, I would have to make the sources dependant on the
> kdebase sources, which is not right.
>
> What should I do?  Shouldnt ContactEntry be defined within kdelibs?

There's also a copy kicking around in 
kdepim/kpilot/conduits/abbrowserconduit, since we needed the same structures 
for accessing the DCOP interface of abbrowser from the KPilot abbrowser 
conduit. So eventually that will have to be cleaned up and moved to the new 
API as well. I'm still concentrating on getting the existing version to work, 
though, with KDE 2.2 KAddressbook.

[Aside #1]
DCOP stub implementations would be useful as well in kdelibs / kdebase. In 
order to use the DCOP interface of KAddressbook conveniently, I had to copy 
the DCOP interface file from there and generate _stub files for use in the 
abbrowser conduit. Really, any application with a serious DCOP interface 
should install its DCOP interface definition somewhere.

[Aside #2]
Mark, let me take a moment to say that you seem to be making tremendous 
strides in this contact-pinning feature, and that *already* you've made a 
valuable contribution to the KDE-PIM project. You could serve as a model of 
inspiration for more users confronted with the developer's comment "send in a 
patch".

[ade]
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim