On Sun, 2002-09-22 at 19:18, Jeffrey Stedfast wrote:
Evolution doesn't use seahorse (or any of it's code) to do GPG support,
That's not really true. The original patch for evolution gpg support
included a large chunk of seahorse code, and there are still some
recognizable pieces left.
No one answered this last time I posted, so here it is again:
I've been told that evolution used seahorse code for implementing its
gpg support. I'm currently working a version of seahorse for gnome2,
and then a bonobo component for it, and I'm wondering if a gnome2
evolution would want to use
Evolution doesn't use seahorse (or any of it's code) to do GPG support,
it uses my own gpg interface library.
http://cvs.gnome.org/bonsai/cvsblame.cgi?file=evolution/camel/camel-gpg-context.crev=root=/cvs/gnome
You are of course welcome to take anything you want from there, but if
Seahorse is
Will gnome2 evolution have a plugin framework?
My (maybe too lofty) goal is to have seahorse2 (which is using gpgme) be
the default gnome2 gpg interface. So, if there's any way seahorse could
be used in evolution to do the gpg support, let me know and I'll see
what I can do to facilitate that.
What does seahorse provide?
e.g. configuration, key handling, etc gui?
If we dont need it to perform signing/verification etc then it might be
a possibility, or if there's some detatched, thread-safe, helper-api to
do the work, etc. (tho that part of the code is quite small).
If it just
I'm not sure if it currently is thread safe, but I have a set of helper
methods that can make signing and verification a bit easier than gpgme,
plus a passphrase callback setup. There's plenty of key handling
functions, such as listing (loads up a GList), generate, delete, export,
import, edit
