Bug 5790 - confusing that the ThinLinc Client isn't associated with opening the configuration file it creates
Summary: confusing that the ThinLinc Client isn't associated with opening the configur...
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: 4.5.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Pierre Ossman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-05 14:14 CET by Karl Mikaelsson
Modified: 2016-02-09 10:44 CET (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Karl Mikaelsson cendio 2016-02-05 14:14:31 CET 
We've got an odd thing going on here, where tlclient saves a configuration file called tlclient.conf, but is associated to open configuration files with a .tlclient extension.

It would be nice if we could figure out something that means that tlclient configuration files created by the client can be copied and reused without having to change their extension.
Comment 1 Karl Mikaelsson cendio 2016-02-05 14:20:01 CET 
Rephrasing the summary.

We've registered the application/vnd.cendio.thinlinc.clientconf MIME type.

https://www.iana.org/assignments/media-types/application/vnd.cendio.thinlinc.clientconf
Comment 2 Pierre Ossman cendio 2016-02-09 10:44:13 CET 
There is no consensus if it should be possible to open this file or if tlclient.conf and the .tlclient files should be separate concepts. We need to decide what we want and then make sure this is clear for the users.
Note You need to log in before you can comment on or make changes to this bug.