[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Move DCOP interfaces to kdelibs?
From:       Cornelius Schumacher <schumacher () kde ! org>
Date:       2001-05-06 19:40:59
[Download RAW message or body]

On Sunday 06 May 2001 20:07, David Faure wrote:
> On Sunday 06 May 2001 12:46, Cornelius Schumacher wrote:
> > Would it make sense to move the DCOP interfaces of applications
> > like KMail to kdelibs?
> >
> > This would make it possible to use the automatically generated stub
> > classes when calling KMail DCOP functions, which is much easier and
> > less errorprone than using DCOP directly.
> >
> > At the moment it's not possible to use the KMail DCOP stub class
> > outside of kdenetwork, because it requires kdenetwork to be
> > installed before compiling the applicaton using the KMail stub.
> > This is not necessarily always the case.
>
> I think it would make sense to have a generic interface in kdelibs,
> like we have the Part, BrowserExtension and especially TextEditor
> interfaces. A new MailClient interface would provide a generic way to
> speak to (or even embed) a mail client.
> Putting KMail-specific DCOP interface is only useful to KMail itself,
> whereas a generic interface extends this to "any mail client".
> And we can't put every app's DCOP interface in kdelibs :)

Agreed. I was also thinking about generic interfaces. KMail was just 
the only example of an KDE mail client, which came to my mind :)

What I would need would be simple interfaces to a mail client and an 
address book client. At the moment I'm duplicating stub code of KMail 
in KOrganizer. That's not good, but I don't see another solution.

-- 
Cornelius Schumacher <schumacher@kde.org>

[prev in list] [next in list] [prev in thread] [next in thread]