Am 18.08.2012, 02:21 Uhr, schrieb Peter Morgan <[email protected]>:
The idea is to only learn mails with a name attached, ie.
Homer Simpson <[email protected]>
but not
[email protected]
to precisely prevent the case where you've a mystic mail contact
without a human readable name for it.
Thats a good idea, but in practice wont work,
for example emails arrive from our carrier in the uk as
[email protected], no name etc, but is also a reply address...
You'll therefore have to add it explicitly - i frankly don't understand
why this is an example why autolearning mails with human names should not
work.
(In case that somehow didn't become clear: this is not an either or
discussion. One can provide the "comfort" of auto-adding contacts w/o
loosing the ability to have the user do so explicitly.
Not necessarily a button, maybe a label..
I got an idea of what it should look like and will attempt to create it
here .. (not a fast c++ coder)
You'll either have to use QWidgetActions or reimplement painting and input
event handling to get interactive elements into a QMenu
I understand that we dont want buttons all over the place, and we could
even do it in a more subtle way..eg colored label adn a context menu
eg
*[email protected] *- Text in green = in address book
*[email protected]* - Text in red = blacklist spam etc
*[email protected] *- Text in black = not in address book
This seems to address the mail header, where a button would not even be a
major issue.
Also afaics it was so far not suggested to learn incoming mail addresses
at all.
My concern was: how would you use trojitá to get an address out of the
addressbook.
a) you've a mail from that contact, thus a button "remove from
addressbook" int the header, thus no problem
b) you don't have a mail from that contact, but the address keeps showing
up in the address completer.
I do not believe that there's a sane and mass compatible ("obvious") way
to get the address away from there.
Just the delete key is troublesome, because you could have selected an
address but actually intend to delete a char in the lineedit.
A context menu on a popup menu is possible but nobody would usually try to
do this.
A button or similar entry in a popup is uncommon and -while possible-
will clutter the list that you usually just want to scan to select a
recipient.
The natural approach in our ultimately lucky case would be a submenu, but
it will be necessary to adjust the popups reactio to user input (so the
submenu does not auto-open when you just select the entry, nor when
clicking it or pressing enter since that should likely add the recipient
etc.)
a good example ... is a client company of mine and they changed domains..
Its been an incredible pain for everyone involved.. Outlook sucks
The beauty of the abook format is that
sed -ie 's/@nukedcompany.com/@shinybrandnew.com/g' ~/.abook/adressbook
would "fix" that problem
The other thing I'd add, is the possibility of adding a database backend
as the address book.. and is something I am looking at.
You can reimplement the AbstractAddressBook class on top of eg. SQL
Cheers,
Thomas
