It relies on Java for a lot of its functionality, we believe it is lightly used, and many customers confuse it with the HTML client. As such the downsides seem to cancel out any benefit.
The product council approves of removing this functionality. Two requirements though: - An attempt should be made to retain shadowing in tlwebadm, provided it doesn't require a massive effort. - The removed code should be donated to https://github.com/oetiker/tl-extras, if they are interested
(In reply to comment #1) > - An attempt should be made to retain shadowing in tlwebadm, provided it > doesn't require a massive effort. Bug 4928 covers implementing shadowing support for the HTML5 client.
(In reply to comment #2) > (In reply to comment #1) > > - An attempt should be made to retain shadowing in tlwebadm, provided it > > doesn't require a massive effort. > > Bug 4928 covers implementing shadowing support for the HTML5 client. Shadowing does not have to be implemented in the HTML5 client for this. We could keep the native client configuration file generation function and move it into tlwebadm.
Completely removing this feature is probably premature. But we can mitigate some of the most glaring problems: - No Java these days (bug 4521) - Confusion in tl-setup (bug 5190)
We have decided that – once we remove this, we will make it available publicly (likely on GitHub). Preparing for this, we should avoid dependencies on ThinLinc libraries. For example, see bug 8161 comment 32.
Note that tlclient.cgi seems to assume that the file /opt/thinlinc/etc/tlclient.conf.webtemplate is present on the machine running it. This might be something to keep in mind if we move it out of the product. We might want to add some simple error handling for the case where ThinLinc isn't installed.
