On Thu, 5 Dec 2002 01:11:42 +0100 (Romance Standard Time) Vadim Zeitlin 
<[EMAIL PROTECTED]> wrote:

>  I even used it to decode PGP messages (and not only to check signatures).

I did so too...

> On Tue, 3 Dec 2002 22:47:24 +0100 Xavier Nodet <[EMAIL PROTECTED]> wrote:
>
> 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?

By adding '--keyserver-options auto-key-retrieve' (without quotes) to
the options of gpg. Of course, this may take some time (a few seconds),
so it would be better to have something like this: 

  Do you want to automatically retrieve missing keys on server?
    - never
    - ask me (when a key is missing)
    - always

The 'ask me' option has the added benefit that the user knows why it
takes some time to display the message.

>  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?

Actually, I never paid any attention to this dialog, probably because
modules are statically linked...


About GUI, I'm really not a designer, but...

A PGP signature can be good and trusted, good but not trusted (I believe
this is called 'invalid' sometimes), good but expired, missing, or bad. 

I would simply have a GPG button that could be either gray if not used
or the message has no signature or the signature is missing, green for
good signatures, orange for invalid or expired signatures, red for bad
ones.

Maybe hovering over the button could provide some added information
(invalid v.s. expired), some information about the ID of the key, etc.

> 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

Seems a good idea!

>  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?

WinPT has one, which is GPL. I attach it to this message. Mozilla has
some, but I guess they are used in toolbars, and are thus much bigger.

>  Finally, what should the "view filters" be called 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?

Renderers     Seems a little bit complicated, but conveys the idea.
Layers        Actually, in Gimp, you find 'filter layers', I guess.


<<INLINE: winpt2.PNG>>

-- 
Xavier Nodet
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." - Benjamin Franklin, 1759.

Reply via email to