#2100 closed enhancement (fixed)
add a novideo content-type
Reported by: | Nathan Hallquist | Owned by: | Nathan Hallquist |
---|---|---|---|
Priority: | major | Milestone: | 2.5 |
Component: | encodings | Version: | 2.4.x |
Keywords: | Cc: |
Description
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
Attachments (1)
Change History (7)
Changed 3 years ago by
Attachment: | novideo-content-type.patch added |
---|
comment:1 Changed 3 years ago by
Owner: | changed from Antoine Martin to Nathan Hallquist |
---|
comment:2 Changed 3 years ago by
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.
comment:3 Changed 3 years ago by
Component: | android → encodings |
---|---|
Type: | defect → enhancement |
comment:4 Changed 3 years ago by
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.
comment:6 Changed 17 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2100
Note: See
TracTickets for help on using
tickets.
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:
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"?