Having prompts in those two fields gives the user a hint of what (s)he
is expected to put into them. This commit will use the example name
'Jane Doe' and the example contact 'jane.doe@example.com' for both
fields. The text has a faint gray color and will vanish if the user adds
text into the field.
This commit adds a function which makes it possible to add faint gray
prompt to a text field. The foreground color of the prompt's text is the
one of the text field, but half transparent. As soon as text is added to
the text field, the prompt will vanish and it will re-appear when the
text field is emptied again.
To help users understand the purpose of the various fields of this
dialog, tool tips are added by this commit. They provide basic
explanation for the primary controls (name, address/number, account and
group).
Thanks to David Bolton for suggesting the used tool tips text.
Instead of simply failing after clicking OK when adding a contact,
validate the address/ID supplied by the user, show an error and
attempt to correct it.
RFC3261 deprecated this attribute:
[...] The use of "transport=tls" has consequently been
deprecated, partly because it was specific to a single hop
of the request. [...]
Closes#2
Because:
* Technically: addresses with spaces don't exist
* Functionally: a user may add an address with a space in it and wait for an
authorization that would never come
Since Office 2010, IM applications need to write to their own key
below IM Providers. Jitsi's setup was preparing this under HKLM for a
while, now write the actual state where it belongs.
https://msdn.microsoft.com/en-us/library/office/jj900715.aspx