-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 18 September 2002 02:59, Marc Mutz wrote:
> A problem that I see coming up in this area is that I'd like KMail to go
> in the Mulberry direction. A professional and RFC-compliant mail client
> that leverages the _full_ potential of MIME. Giving the user full
> control over the MIME tree in the composer kind of thing. That, of
> course, will repeatedly set Aaron and myself on opposing seats, but I
> hope to solve such problems in discussion.

why? "nice, usable" and "powerful"  are not mutually exclusive when it comes 
to describing an interface. the only reasons i'd have concerns over allowing 
greater control over the MIME tree in the composer window is if it was 
implemeted in a way that:

  o forced all users to understand MIME tree navigation to compose messages 
(e.g. there wasn't a "just write an email" mode)

  o was painful to use for those who do understand the concept of a MIME tree

the first point is important because the vast majority of KMail's users do not 
now, nor will they ever, grok MIME tree concepts; the second point is 
important because even power users have better things to do than get annoyed 
at their mail client ;-)

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

"Everything should be made as simple as possible, but not simpler"
    - Albert Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9iPdo1rcusafx20MRAlytAJ0Y2GlFlcopMGzAQVfwV9fc0qNERgCbBPEz
LVXhYDb1TPNPUbjffxHiMSg=
=Tbar
-----END PGP SIGNATURE-----

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail