Correct design is an admirable and necessary objective. Without detracting from that goal, I merely wish to register the point that some GnuPG support is better than none. So perhaps it is wise to ask whether M should offer basic GPG support in the near term, with a more full-bodied design in the long term.
It is relatively simple to implement basic GPG support using simple command-line calls to the GPG console tool. In reality this is all many email clients actually do. As an example, here is a screen shot of The Bat! with its very basic GPG interface. http://www.ultimateg.com/Bat_GPG.png The Bat! lets users select between GPG or an internal PGP implementation. The internal key manager only works with the internal PGP code, and that is fine with me. I do not use Bat! for managing keys; there are dozens of GPG front ends capable of doing that. It would be a nice feature, but is not mandatory. (What I do consider mandatory is the option of using a completely external piece of code over which I have full control.) I appreciate the desire to do things right and merely wanted to note how easy a near-term, "stopgap" solution really is. The wxWindows library offers a method to call console tools: "wxProcess ... supports IO redirection of the child process.... GetInputStream, GetOutputStream and GetErrorStream can then be used to retrieve the streams corresponding to the child process standard output, input and error output respectively." Kind regards, Mark ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
