[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:       Ingo =?iso-8859-1?q?Kl=F6cker?= <ingo.kloecker () epost ! de>
Date:       2001-10-29 21:43:32
[Download RAW message or body]

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

On Monday 29 October 2001 17:37, Michael Häckel wrote:
> > I'm currently not concerned with those high-level plugins (under
> > which I'd put a key manager (for e.g. Sphinx), too.), but the KMime
> > part of this. I'd like to have a single body part class which
> > interfaces to {the cryptographic plugin,gpgme}. Let's talk 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?

As I don't know what exactly Marc has in mind I can't comment on this. 
With kpgp it's also possible to encrypt/decrypt/sign/verify via the 
various kpgpbase classes.

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

iD8DBQE73c2EGnR+RTDgudgRAp8EAKCp9nP8b+OxPCmpfEZXI9BUsDaqDACfaFaP
L2ewSMrOQ2B2kUzqLlNwIxc=
=8mVU
-----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]