New ThinLinc Versions / Development Roadmap

[samuel]

@blacksnow

Profile Saving, I think this has probably been mentioned elsewhere on the forums.
1.a) Switching between multiple logins and remembering all the hostnames is a bit tedious. I don’t really care about password management so much but I would prefer to have a dropdown of previous hostnames I’ve connected too.
1.b) Setup a default screen resolution for newly initialized sessions per profile.
1.c) Drive/Sound/Clipboard options per profile, for example on some connections I don’t want to have my drives connected, nor sound transferred, nor clipboard sharing capability for security reasons or otherwise.

Hi @blacksnow!

While this might not be precisely what you are looking for, I think it might help; you can create shortcut files with separate configurations for different hostnames. The files could, for example, be server1.tlclient and server2.tlclient and effectively work as different profiles. Files ending with .tlclient are associated with the ThinLinc client.

1. Create an empty file with the suffix “.tlclient” (*).
2. Double click it to open the ThinLinc client.
3. Make any changes you want to the settings.
4. Connect to your server.
5. The username, hostname, and settings are now saved to the shortcut file.
6. Repeat steps 1-4 for other servers or settings.

(*) Note that GNOME has a bug preventing file associations for empty files from working. If using GNOME/Nautilus, you can work around this issue simply by adding a space to the .tlclient file after creating it. 7301 – empty .tlclient files are not associated at all

1.d) Possibility to separate transferring local microphone and remote sound? In some cases I want to hear the remote system’s sound but I don’t want to transfer my microphone. Again for security reasons and bandwidth.

I see your point, it is a good idea. I added a feature request entry to our systems for this. However, I don’t think a fix can be expected in the short term unless we see more user interest.