Finish v1.1.0

Author: pinhead84

.idea/misc.xml

@@ -1,6 +1,21 @@
 Changelog for Remote Support Tool
 =================================
 
+1.1.0 (20 Mar 2019)
+-------------------
+
+-   upgrade to Java 11
+-   update [Commons Text](https://commons.apache.org/text/) library to version 1.6
+-   update [JSch](http://www.jcraft.com/jsch/) library to version 0.1.55
+-   update [Simple Logging Facade for Java](https://www.slf4j.org/) library to version 1.7.26
+-   provide sh application launcher for macOS ([issue #20](https://github.com/OpenIndex/RemoteSupportTool/issues/20))
+-   tab key is not sent to the customer application ([issue #21](https://github.com/OpenIndex/RemoteSupportTool/issues/21))
+-   enable / disable transfer of keyboard & mouse inputs ([issue #22](https://github.com/OpenIndex/RemoteSupportTool/issues/22))
+-   rework transfer of keyboard inputs ([issue #23](https://github.com/OpenIndex/RemoteSupportTool/issues/23))
+-   prefer Nimbus look & feel on Linux ([issue #25](https://github.com/OpenIndex/RemoteSupportTool/issues/25))
+-   set awtAppClassName for Gnome / Ubuntu Unity ([issue #26](https://github.com/OpenIndex/RemoteSupportTool/issues/26))
+
+
 1.0.1 (13 Mar 2019)
 -------------------
 
@@ -11,12 +26,9 @@ Changelog for Remote Support Tool
 -------------------
 
 -   migrated from Tcl/Tk to Java
--   implement the whole support session in Java, no need for external 
-    applications (x11vnc, OSXvnc, TightVNC, OpenSSH)
--   provide a graphical interface for both sides of a support session 
-    (customer & support staff)
--   provided binaries are bundles with a stripped down version of the
-    OpenJDK runtime environment (version 10)
+-   implement the whole support session in Java, no need for external applications (x11vnc, OSXvnc, TightVNC, OpenSSH)
+-   provide a graphical interface for both sides of a support session (customer & support staff)
+-   provided binaries are bundled with a stripped down version of the OpenJDK runtime environment (version 10)
 -   provide a signed application bundle for macOS
 -   switched from MIT to Apache License 2.0
 
@@ -27,23 +39,19 @@ Changelog for Remote Support Tool
 -   migrated from Python to Tcl/Tk
 -   replaced Paramiko with OpenSSH
 -   implemented a new build process based on Tclkit
--   updated to OSXvnc 5.0.1, which should fix problems with Retina displays on
-    Mac OS X
--   rebuild x11vnc, which should fix problems with a missing libxss library
-    on amd64 based Linux systems
+-   updated to OSXvnc 5.0.1, which should fix problems with Retina displays on Mac OS X
+-   rebuild x11vnc, which should fix problems with a missing libxss library on amd64 based Linux systems
 -   added some more options for GUI configuration via config.ini
 
 
 0.4.1 (10 Nov 2015)
 -------------------
 
--   translated into Italian
-    (thanks to [Sjd-Risca](https://github.com/Sjd-Risca))
--   compatibility fixes for PyInstaller 3
-    (thanks to [Sjd-Risca](https://github.com/Sjd-Risca))
+-   translated into Italian (thanks to [Sjd-Risca](https://github.com/Sjd-Risca))
+-   compatibility fixes for PyInstaller 3 (thanks to [Sjd-Risca](https://github.com/Sjd-Risca))
 -   rebuilt with PyInstaller 3 on all supported platforms
 
 0.4 (17 Jun 2015)
 -----------------
 
--   first public relase
+-   first public release

.idea/runConfigurations/Clean.xml

@@ -3,25 +3,15 @@
 
 ## Notes about branches
 
-This project follows the principles of the 
-[GitFlow branching model](http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/)
-as [proposed by Vincent Driessen](http://nvie.com/posts/a-successful-git-branching-model/). According to this model you 
-will find these branches at the GitHub project page:
+This project follows the principles of the [GitFlow branching model](http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/) as [proposed by Vincent Driessen](http://nvie.com/posts/a-successful-git-branching-model/). According to this model you will find these branches at the GitHub project page:
 
--   The [master branch](https://github.com/OpenIndex/RemoteSupportTool/tree/master) contains the current stable 
-    releases. No development is directly taking place in that branch.
+-   The [master branch](https://github.com/OpenIndex/RemoteSupportTool/tree/master) contains the current stable releases. No development is directly taking place in that branch.
 
--   The [develop branch](https://github.com/OpenIndex/RemoteSupportTool/tree/develop) represents the current state of 
-    development. Changes from this branch are merged into 
-    [master](https://github.com/OpenIndex/RemoteSupportTool/tree/master) when a new version is released.
+-   The [develop branch](https://github.com/OpenIndex/RemoteSupportTool/tree/develop) represents the current state of development. Changes from this branch are merged into [master](https://github.com/OpenIndex/RemoteSupportTool/tree/master) when a new version is released.
 
--   For more complex features you may also find different feature branches. These are derived from
-    [develop branch](https://github.com/OpenIndex/RemoteSupportTool/tree/develop) and are merged back / removed as 
-    soon as the feature is ready for release.
+-   For more complex features you may also find different feature branches. These are derived from [develop branch](https://github.com/OpenIndex/RemoteSupportTool/tree/develop) and are merged back / removed as soon as the feature is ready for release.
 
-> **Notice:** If you like to provide changes to this project, you should always use the 
-> [develop branch](https://github.com/OpenIndex/RemoteSupportTool/tree/develop) as basis for your customization. Feel
-> free to create separate feature branches for any custom feature you like to share. 
+> **Notice:** If you like to provide changes to this project, you should always use the [develop branch](https://github.com/OpenIndex/RemoteSupportTool/tree/develop) as basis for your customization. Feel free to create separate feature branches for any custom feature you like to share. 
 
 
 ## Create a pull request
@@ -40,10 +30,10 @@ We love pull requests. Here's a quick guide.
  
 -   [Submit a pull request](https://github.com/OpenIndex/RemoteSupportTool/compare/) with the changes from your fork.
 
-At this point you're waiting on us. We like to comment on pull requests as soon as possible. We may suggest some changes 
-or improvements or alternatives.
+At this point you're waiting on us. We like to comment on pull requests as soon as possible. We may suggest some changes or improvements or alternatives.
 
 Some things that will increase the chance that your pull request is accepted:
 
 -   Test your changes.
+
 -   Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).

.idea/runConfigurations/CustomerTool.xml

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright 2015-2018 OpenIndex.de
+# Copyright 2015-2019 OpenIndex.de
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -20,5 +20,5 @@ DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
 
 set -e
 export LANG=en
-cd ${DIR}
-${MVN} clean
+cd "$DIR"
+"$MVN" clean