Re: [Usability] Mail clients put the Subject field in the wrong place

[Hynek Hanke <hanke brailcom org>]

> > Hynek was using Evolution, a mail client that -- like most mail clients
> > -- puts the Subject field above the message body in the composition
> > window. As long as mail clients do that, and as long as humans go
> > through forms top-to-bottom, it won't be surprising that they usually
> > don't use the Subject line to summarize a message that they haven't
> > even written yet. 

Well, shouldn't the To: field also be at the end then? ;)
Like ``I want to write something to someone. Ok, I will write it,
then I will think what it is and whom do I want to send
it to...'' :)

No, please. If I'm going to write a message to somebody,
then it's a very good idea to at least know a little what
I'm going to write about. Placing the Subject: line at the
beginning is *very logical*. I first think of whom I'm going
to send a message, what's the subject of the message etc.,
only then I think of how exactly am I going to formulate
the message I want to convey.

It's true, sometimes people write messages that are not
about something in particular. Like some ,,hello, I'm fine.
how are you? there is this and that new in my life etc.'',
and then it might be a good idea to leave filling in the
subject line to the end. I don't know what's the percentage
of these emails for different kinds of users, but for many emails,
the first approach is far superior.

I'd very much prefer people posting to conferences, posting workmail or
other ``useful'' stuff, to be able to decide what they are going
to write about and only then start to type on their keyboard!

I've already explained the mistake by which I've sent a no-subject
message. Stupidity on my side, definitely.

Kalle Vahlman suggested:
>"Send" should be disabled until the message is ready for sending, and
> unless it has a subject line, I wouldn't consider it ready. The fact
> that it's the subject that is missing can be hinted visually (with
> accessibility options in mind of course).

I think this makes sense. My only concern with these disabled ``shaded''
buttons is that sometimes I have a button that I want to press and
it's not possible and it's not clear to me why. Of course this case
would be obvious for me, but maybe not for other users. It would be very
nice if the button would provide me with some information on why it is
inactive. Like if I go over it with my mouse, it would say: Send -- you
need to fill in the subject line. Additional visual hints elsewhere are
maybe nice too, but the basic is having *the button* associated with the
hint of why it is inactive.

With regards,
Hynek Hanke