Xpra: Ticket #2100: add a novideo content-type

Some of my users really dislike video frames in xterm. With this patch, users can (1) set a novideo content type and (2) set a guesser rule from an environment variable (from a systemd entry I have):

Environment=XPRA_CONTENT_TYPE_DEFS=class-instance:xterm=novideo


Mon, 07 Jan 2019 22:53:03 GMT - Nathan Hallquist: attachment set


Tue, 08 Jan 2019 04:00:23 GMT - Antoine Martin: owner changed

I like the idea.

We could just add a new flag like TEXT_NOVIDEO. This would apply to all applications that are meant to be text.

This does not use lossless:

            return nonvideo(info="lossless content-type")

It will use a non-video encoding, usually at a high quality setting, but not lossless unless you change the quality value with this call. And if you do, then you might as well call the new content-type "lossless"?


Tue, 08 Jan 2019 18:35:29 GMT - Nathan Hallquist:

I had originally gone with lossless and then changed my mind after trying nonvideo and finding myself happy with that. I forgot to change the text is all.

I am okay with either choice. I defer to you.


Tue, 08 Jan 2019 18:36:28 GMT - Nathan Hallquist: type, component changed


Wed, 09 Jan 2019 15:42:07 GMT - Antoine Martin:

The part adding an env var for specifying content type definitions was merged in r21302 (see ticket:1950#comment:8). r21303 disables video encoders for windows with the "text" content-type hint.

@nathan_lstc: does this work OK for you? if so, please close.


Wed, 09 Jan 2019 17:53:35 GMT - Nathan Hallquist: status changed; resolution set

This is great! Thank you.


Sat, 23 Jan 2021 05:42:12 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2100