Re: [Evolution-hackers] [Fwd: Re: [evolution-patches] [PATCH] IMAP preauth and subcommand connection.]

[David Woodhouse <dwmw2 infradead org>]

On Tue, 2003-07-22 at 14:09, Ettore Perazzoli wrote:

> Hmm actually this might work if we make the wording clear enough.
> (E.g. For the command-part, maybe it should probably just be called
> "Advanced..."?)

I think I prefer 'Custom Command', since 'Advanced' could mean many
other things. 

I'd like to see:

 Connection type:     [ Unencrypted ]
                      [ Encrypted if possible ]
                      [ Always encrypted ]
                      [ Custom connection command ]

I think the last of those four options is sufficiently clearly implying
"You don't want me" for the naïve user -- using the word 'Advanced'
probably doesn't make that fact clearer. 

> Maybe we could also use a morphing option menu a la OS X here.  I.e.:

Cute, but probably overkill ;)

> > Or the host/username fields could be available as '%h' '%u' in the command
> > string ...
> 
> This would work well with what I proposed above; we could advertise the
> "%h" and "%u" with a little blurb in the "advanced" dialog.

True -- but don't we have context-specific help already? And a suitable
default _using_ them will make it obvious too.

I'm inclined to suggest something like the mockup at 
 http://www.infradead.org/~dwmw2/config-mockup.jpeg

In the case where the connection type is set to something other than
'Custom command', we can either grey out or completely remove the text
entry box for the actual command -- and when we first enable 'Custom
command' the text entry box for it comes back, with the sane default
which makes the $URLHOST and $URLUSER stuff obvious.

Does that seem reasonable?

-- 
dwmw2