When creating tl-run-winapp applications in TLDC, one usually wants to set the
correct icon. Then you need to somehow "extract" the icon from the .exe and
transfer it to the ThinLinc servers. Currently, we have no tools or
documentation on how to do this. I think we should have.
There's a Linux tool called "icoutils" than can do this. The magic command is:
wrestool -x --type=14 file.exe | icotool -x -
The result is several .png files, for different sizes and color depths. We could
include icoutils in ThinLinc, in one way or another.
One problem is that the .exe files are not actually available on the ThinLinc
servers. (If they were, it would also be possible to *browse* to the correct
file, instead of having to type it in by hand. A big improvement.) So, how to
reach the .exe from ThinLinc? There are two usable protocols:
1) CIFS. TLDC could call "smbclient". Or, we could create a link to "konqueror",
which supports CIFS. One problem: Which user should we authenticate as? The
simple solution is just to popup a username/password dialog, and let the admin
decide. CIFS *might* be disabled altogether, though. Another problem: It's not
very easy to get the local, absolute path from a CIFS path. If the servers
shares \\server\programs, and we find \\server\programs\app\app.exe, how do we
know if this file is c:\program\app\app.exe or c:\program files\app\app.exe?
2) RDP, somehow. We can trust that RDP is active and available; otherwise
tl-run-winapp won't work anyway. I don't really know how to browse & download
files via RDP, though. The RDP drive redirection works "the wrong way". It might
also be disabled.
Tricky. I wonder how Tarantella solves this, if they do.
The webmin interface could be an extended version of Webmins built-in chooser.cgi.
For 1.5.0, we should provide a limited functionality: Implement a feature for
transferring exe:s from a WTS is too hard for 1.5.0, though. But, we could
provide a simple script for extracting icons in 1.5.0. And we should probably
Another possible solution is to allow users to upload the exe file to the webmin
interface, which would then extract the ico and put it in a predefined folder on
the server disk, and then let the generated .desktop file point to that disk folder.
This is a simple solution that would make life easier for the administrator,
while still being quite simple to implement.
Gah! This bug is too unspecific.
The browsing part is now covered by bug 1682.
rdesktop (and associated tools) is being removed from the ThinLinc product.