Investigate SIXEL support
By gnach... on October 14, 2014 05:46 (imported from Google Code)
Activity
Comment 1 by u...@zuse.jp on October 16, 2014 13:18
@Saitoha, can you explain how your thing works? It seems to go well beyond the sixel spec.
We just only used existing DEC's features and some traditional image processing techniques.
In view of terminal spec, our answer is very simple.Example: https://www.youtube.com/watch?v=hqMh47lYHlc
Patched FFmpeg in above demo runs the following procedure.
- emits a CUP sequence(move cursor to [1, 1]).
- emits DECSIXEL sequence (only 16 color register were used. it's considered VT340 compatible).
- return to 1.
In view of image processing, we have done many trials and errors(scene change detection, color quantization, high quality dithering, high compression achievement, ...etc). But they are not terminal issue.
-
Comment 2 by u...@zuse.jp on October 16, 2014 13:27
Example2: https://www.youtube.com/watch?v=UOTMGdUPYRo
In above demo, we also used "DEC Locator mode" to retrieve mouse coordinates in pixel units.
See http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#Mouse%20Tracking -
Comment 3 by u...@zuse.jp on October 16, 2014 13:32
Example3: https://www.youtube.com/watch?v=QQAqe32VkFg
In this demo, we also used "Left-Right margin mode"(DECLRMM) to scroll vertical-splitted region with SIXEL images. It is already supported by iTerm2. -
Comment 5 by u...@zuse.jp on October 18, 2014 08:29
I request the following control codes and features.
- DECSIXEL sequence (DCS P1;P2;P3 q ... ST)
In DEC's style, DCS sequences are parsed as the following scheme:
DCS P .... P I .... I F D...D ST
3/0-3/15 2/0-2/15 7/0-7/14(http://odl.sysworks.biz/disk$vaxdocdec953/decw$book/d3qsaaa1.p26.decw$book#102)
VT100DCSParser.m might had better follow it.
-
DEC Locator mode
It is an option, but this would be required by some GUI-flavored terminals applications(such as Example2).
This feature requires the following set of control codes.
DECELR
DECSLE
DECRQLP
DECEFR -
Set pixel size with TIOCSWINSZ
Now iTerm2 doesn't set its own pixel dimentions of client area to (winsize.ws_xpixel, winsize.ws_xpixel) with TIOCSWINSZ ioctl.
Some terminals such as Terminal.app or Xterm does that.
If iTerm2 do it, terminal applications can get terminal pixel size over TIOCGWINSZ ioctl.
This technique is already used by ranger(https://github.com/hut/ranger/blob/master/ranger/ext/img_display.py#L117).
Although applications can be use CSI 14 t/CSI 18 t instead of it, I think that's not a proper way. -
Changing Primary DA report
If we implement SIXEL or DEC Locator, we should change the report for device attributes request (ESC [ c).
mentioned in issue #3543 (closed)
changed milestone to %Review for next version
