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

List:       kmail-devel
Subject:    Re: Bug#24532: integration of kmail with knode
From:       "Aaron J. Seigo" <aseigo () mountlinux ! com>
Date:       2001-04-23 19:52:49
[Download RAW message or body]

Hi..

> Basic newsgroup support in KMail would be very much welcomed from my
> side. News is indeed not much different from mail (the format is very

i would agree w/this.. i do not use usenet much, but i think that pooling 
devel efforts and cutting down the code base could be a boon to overall kmail 
development as well as enhance the user's experience.

> A very uneducated guess from my side is that KNode and KMail share
> approx. 90% of the GUI, 50% of other code (PGP, transport, folder
> handling,...) and 80% of config options. From a code-reuse POV it's

as for the 80% config options thing... i suppose that now is as good a time 
as any to let people know that i'm quietly working on extending kcmemail 
quite substantially with the aim of having it featureful enough to be usable 
by any email-aware app as the user's email settings ... from there, kmail can 
use the kcmemail identities instead of its own. the benefits to this as i see 
them would be:

  - better integration between kmail and the desktop as a whole
  - opens the possibility of kmail using kio_smtp properly as well as being 
able to take advantage of advanced features in other kio slaves already in 
use
  - cuts down on the code in kmail and helps eliminate a bit of code dupe 
between kcmemail, kmail and every other email app that may appear for kde

i would also like to see something similar happen to the pgp settings 
evetually as well (e.g. have them put in the crypto kcontrol)

as a side note (and back to the original topic), for a knode/kmail 
integration to work well, i think that some refactoring would be in order for 
the KMFolder class (and perhaps KMFolderNode and KMFolderDir as well...) ... 
even now it looks a little hackish in there w/IMAP support, but nothing that 
a little cleaning up and design touch-ups wouldn't cure.

as a closing question (and back to being off topic again): is anybody else 
working on kcmemail<->kmail integration that i should know about? is there 
any reason why this shouldn't be done? (just in case i'm missing some glaring 
reason; i've noted all the places in the kmail code base i'll need to touch 
and it doesn't look all that horrible) i've talked to the devel who was 
previously working on kcmemail and have coordinated it with him, so now might 
be a good time to start coordinating this with the kmail folk =)

-- 
Aaron Seigo
_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail

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