For some cases, it would be convenient if the ThinLinc client remembered the last n servers it has connected to. The servers could be presented in a dropdown box similar to the one in Mozilla (for the URI field). This would be convenient for example for support personel using ThinLinc to connect to servers located at several different customers. This applies to both Borås Sjukhus (which has requested the feature), and to ourselves.
We should consider generalizing this bug: Provide a profile manager that can handle different settings for different servers as well. It could be implemented as a separate application, calling tlclient.
VMware has an interesting feature: The configuration files for the virtual machines are executable, and begins with: #!/usr/bin/vmware This could perhaps be useful with tlclient as well: You could have several different config files, and by executing these, you'll bring up the client with the defined settings.
The solution with #!/usr/bin/vmware doesn't work, because /usr/bin/vmware is a shell script. We will have the same problem with tlclient.
"#!/usr/bin/env vmware" works.
Since we have implemented bug 2618, this functionality is basically available. We might want to consider some GUI manager tools, though.
See bug 5503 for simply having a list of recently used servers, without a connection to any other settings.
Microsoft solved this by having a separate application for handling different connections: https://learn.microsoft.com/en-us/sysinternals/downloads/rdcman That could be an option that keeps things modular, and keeps the complexity away from standard users. They tell people to avoid this and just use one of their standard clients, though: https://learn.microsoft.com/en-us/troubleshoot/windows-client/remote/use-mstsc-universal-remote-desktop-client-instead-rdman This might be wishful thinking, as I've not seen any connection manager in the standard mstsc. Their new "universal" client has an interface focused on multiple machines, though. At the cost of making the simple case more confusing.