On Tue, 3 Dec 2002 22:47:24 +0100 Xavier Nodet <[EMAIL PROTECTED]> wrote:
XN> This seems to be a good start, for someone that "really does not know
XN> this stuff"... :)
I am reasonably confident that we're going to have rudimentary support for
PGP quite soon (although there are many things left to do), but I'm
absolutely not sure that this is the best way to implement it. For example,
I don't know how to avoid code duplication between PGP view filter and
whatever is going to process APPLICATION/PGP-SIGNATURE attachments --
clearly the code should be shared somehow...
XN> I managed to verify the signature I added to the first
XN> message in this thread. And the '- ' was removed, of course.
I even used it to decode PGP messages (and not only to check signatures).
Why do you think I suddenly decided to work on PGP support -- I finally had
an excuse to do it as I got mail from someone using it ;-)
XN> One little thing that we must keep in mind is an option so that
XN> unknown keys encountered by GPG are downloaded automatically.
How can this be achieved?
Anyhow, we do need a configuration dialog for PGP engine -- and also for
PGP (and other) view filters. The problem is how should it be accessible?
Maybe from (currently quite useless) "Edit|Modules..." dialog?
XN> I really don't have time to code
It's a pity you can't write code because I have very clear ideas about
what needs to be done :-) I'm going to write them down just to not forget
them and also to invite any comments. So, the plan is:
1a) add configuration for the view filters (UI to determine)
b) configuration dialog of the PGP filter should provide access to the
one for the PGP engine
2. add "active content", i.e. stuff which appears like icons in the
viewer and which can be clicked to see some info about them: this
would be useful for showing PGP signature, for example.
--- probably release 0.65 here ---
3. make Composer inherit from (or contain a) MessageViewer: this is the
most important architectural change left to do. I don't know why hadn't
I thought about this before but it's clear that this is how it should
be: it's the only way to avoid duplicating PGP decoding code in the
composer as well, for example -- like this it is simply going to start
with the text which was (or would have been: there is a subtlety here
as you can reply without opening the viewer first) shown in the viewer
4. add support in the composer for the encryption -- maybe using some
"post composing filters" (spell checker might be one of them as well)?
XN> but if I can help...
You can by inventing a nice GUI for all this stuff. I still have no idea
about how to do it. Again, the requirments are that the view filters be
easily accessible for turning on/off and configuring. But how to do it?
Also, I'll need some icons (for PGP signature icon in (2) and also I'd
like to have icons for all the view filters) and I know I'm going to lose
a lot of time looking for them. Could someone please help?
Finally, what should the "view filters" be caleld at the UI level? Calling
them filters is going to be very confusing (I thought about renaming
(message) "filters" to "rules" but this is too much work), so we need
something else. Any ideas?
Thanks,
VZ
-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET
comprehensive development tool, built to increase your
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
_______________________________________________
Mahogany-Developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mahogany-developers
