Theory and Practice of Sprixels: Difference between revisions
No edit summary |
|||
| Line 8: | Line 8: | ||
==Sprixel flavors== | ==Sprixel flavors== | ||
There are at least four | There are at least four implemented protocols: | ||
* the venerable DEC [[Sixel]] protocol, introduced on the VT125, and also present on at least the VT240 and VT330. Implemented by at least XTerm, Mlterm, wezterm, and foot | * the venerable DEC [[Sixel]] protocol, introduced on the VT125, and also present on at least the VT240 and VT330. Implemented by at least XTerm, Mlterm, wezterm, and foot | ||
** with patches out for at least VTE, alacritty, and Windows Terminal. | ** with patches out for at least VTE, alacritty, and Windows Terminal. | ||
* Kitty's protocol, advanced by Kovid Goyal. | * Kitty's protocol, advanced by Kovid Goyal. | ||
* The "1337" iTerm2 protocol, also implemented by wezterm. | * The "1337" iTerm2 protocol, also implemented by wezterm. | ||
* | * The [https://gitlab.com/klamonte/jexer/-/wikis/jexer-images Jexer Image Sequence] from Autumn Lamonte's Jexer | ||
Additionally, you can shit <i>con brio</i> all over the Linux framebuffer directly when in a framebuffer console, though I wouldn't call this a protocol. Christian Parpart (associated with Alacritty) is working on his " | |||
"[https://github.com/christianparpart/terminal-good-image-protocol/ Terminal Good Image Protocol]", but it has not yet AFAIK seen implementation. | |||
Having waded in the velvet seas of terminal graphics protocols for a minute now, I've been putting some of my own thoughts down as [[STEGAP]]. | |||
===Sixel=== | ===Sixel=== | ||