Closed fredricocalamari closed 4 months ago
That would be really hard to maintain, because I would need to change the template every time I changed a viewer parameter. The parameters and their default values are all documented in the TurboVNC Viewer usage screen, and that usage screen is generated automatically from the parameter definitions inside of the source code. The problem with a template is also where to install it. There is no central location for .turbovnc files, so the only logical place to install the template would be in the documentation directory (where it is unlikely to be seen.) Leaving it in the source directory serves no purpose, since a user could more easily get that information from the TurboVNC Viewer usage screen or by simply looking at java/com/turbovnc/rfb/Parameters.java. I would be open to automatically creating an HTML version of the TurboVNC Viewer usage screen somehow, so it could be linked from the TurboVNC User's Guide. However, the whole point of the .turbovnc file format was to allow parameters and values to be specified exactly as they are specified on the command line, so providing a template seems a little pedantic.
this should help creating configuration files