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

List:       kmail-devel
Subject:    Re: kdepim depends on kdenetwork through mimelib
From:       "Mauro DePascale" <mauro.depascale () marconi ! com>
Date:       2002-09-03 6:00:33
[Download RAW message or body]


I think that many other components of KMail can became shareable with other
apps . . .

For instance, consider just an applet to check for mails, or the ability to
directly send a document as an e-mail into koffice, or the option to
communicate to all the attendees of a meeting a notification mail into
kpim. In all these cases, there's need for configuring and managing mail
accounts and the problem of implementing communication with the
corresponding KIOSlaves, problems already solved (well, the notes part not
yet . . .:-((() and available into KMail.
I think it would be very nice to have a centralized account management (on
a per user basis) shareable with all the other applications, in this way a
user will have to configure its groupware accounts just once.

On the other hand, I already started looking what would be required to
accomplish the task: it's a nightmare (at least for me)! I think that
implementing such centralized management would require a lot of work, in
particular, I see as a very complex task to define a common API to export
account management functionalities, keeping it flexible but also feature
rich.

Larry


PS
Well, It's a long time I've this idea in mind, now that I've exposed it,
feel free to flame me as you like !




Don Sanders <sanders@kde.org>@mail.kde.org on 03/09/2002 03.41.25

Please respond to kmail@mail.kde.org

Sent by:  kmail-admin@mail.kde.org


To:   kmail@mail.kde.org, kde-core-devel@mail.kde.org, "Best, Jan-Pascal
      van" <j.p.vanbest@tbm.tudelft.nl>
cc:

Subject:  Re: kdepim depends on kdenetwork through mimelib


On Tuesday 03 September 2002 05:09, Marc Mutz wrote:
<snip>
> On Monday 02 September 2002 11:29, Best, Jan-Pascal van wrote:
> <snip>
>
> > Since mimelib is part of kdenetwork, this means that kdepim
> > now depends on kdenetwork. To resolve this, I would propose
> > to move mimelib from kdenetwork to kdelibs. Would you agree
> > to that? And if you do, how should I go about doing that
> > properly?
>
> <snip>
>
> Oh, I didn't know it's April 1st :-((

It really was a classic moment I didn't know whether to laugh or cry.

> Here, you have a strong vote against further mimelib spreading.
>
> Do you need the subject of the mail? Oh, you really _do_ rfc2047
> decoding yourself, aren't you? You need the filename of the
> attachment? Oh, you _do_ rfc2231 decoding, aren't you? Because
> mimelib does _not_.

I agree with marc that mimelib does not belong in kdelibs. But there
is a clear and consistent need for kde-pim and knode/kmail to share a
library. We either need to put all these applications in the same
package or make a new library package that kde-pim and kdenetwork
depend on.

I actually tend to think moving KMail and KNode into a package with
kde-pim makes the best sense. Pity we don't have a better name than
kde-pim, kde-groupware might be better.

Don.

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail



_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]