Defaults to true on Windows if the application is pinned to the
taskbar. Determined by searching for a shortcut with the application's
name in the pin-folder.
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.
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.
This reintroduces some old code in order to give the user the option to
switch between those two behaviours.
It also prevents the removal of all caps nodes (and thusly breaking the
new detection) when a rogue offline presence event comes in. This is
such an event in which a contact is falsely assumed as offline, if the
preferred resource of two or more same prioritised resources goes
offline. We are checking this by looking whether it is a
"resourceChanged"-event. This should probably be changed again, after
those offline presence updates have been fixed.
- Fixed format of comment
...ommunicator/plugin/sipaccregwizz/ConnectionPanel.java
- Changed description of configuration checkbox like ibauersachs has
recommended
* i18n support.
* Show instructions at top of dialog.
* Explicitly say "click here" in hyperlink text for opening approval page.
* Changed text of Done button to "Save". (Depending on i18n.)
To, for one, protect users from accidents and, for two, don't
accidentally send "stupid messages" we do no longer send any messages
starting with '/'. Instead it shows a message delivery failed message
for error UNSUPPORTED_OPERATION. Reasoning is that the intended
operation is either unsupported or unknown. In both cases there is no
support for it, so let the user know.
Initial support for secure connections has been introduced. An extra
package path has been added to the manifest in order to acquire
SSL-related classes. The IrcStack has been modified to receive an extra
parameter indicating whether or not to establish a secure connection.
A number of small UI tweaks have been made to the wizard. User id and
server entered into the "simple form" are now migrated to the full form.
An extra checkbox is added to indicate plaintext/secure connection. The
wizard currently defaults to secure. An appropriate default port is set
based on plaintext/secure type of connection. Registered new listeners
in order to evalute access to Next-button on every change.
Add ability to access TLS cipher suite, protocol name and server certificate using an new OperationSet. Only implemented for XMPP so far. Also makes this information available in the call information frame.