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

List:       kmail-devel
Subject:    Re: [Aegypten] Design of new KMail Plug-In interface
From:       Marc Mutz <Marc.Mutz () uni-bielefeld ! de>
Date:       2001-10-30 10:26:02
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 29 October 2001 22:43, Ingo Klöcker wrote:
<snip>
> > > as if we supported only gpgme. Then such a body part class would
> > > be very easy to write, since it only needs to give
> > > encrypt/decrypt/sign/verify commands to gpgme (In a first step,
> > > this would be using the synchronous interface),  and act
> >
> > Is this really more difficult with kpgp?
<snip>

No. But it's easier when you only need to support _one_ interface (the 
gpgme one), instead of two (the gpgme one and the kpgp one). You can 
hard-code the gpgme interface instead of thinking about another layer 
of abstraction between {gpgme,kpgp} and Multipart::{Encrypted,Signed}.

But that's mood now, since it seems we're going to follow the way 
Karl-Heinz has laid before us...

Marc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE73p0V3oWD+L2/6DgRAg18AKCZxKiB61UpnJv+nsYisGClVkEZ1wCg5tgm
sx5tMLWSjOlUSmrWhFNy67E=
=kutW
-----END PGP SIGNATURE-----

_______________________________________________
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]