Notcurses: Difference between revisions
No edit summary
|Line 311:||Line 311:|
[[File:Notcurses-0.4.0-bling.png|640px|center|Contact sheet from Notcurses 0.4.0 demo]]
[[File:Notcurses-0.4.0-bling.png|640px|center|Contact sheet from Notcurses 0.4.0 demo]]
Revision as of 15:47, 25 June 2021
notcurses is a library for building complex, vibrant textual user interfaces (TUIs) on modern terminal emulators. It does not use Ncurses (though it does make use of libtinfo from that package), nor is it an X/Open Curses source-compatible replacement. It is written in C, with C++-safe headers. Rust, C++, and Python wrappers are available.
- Optional use of "alternate screen" where available (enter_ca_mode/exit_ca_mode terminfo capabilities)
- All APIs use 24-bit 8bpc RGB color natively
- Color is quantized down for indexed palette terminals
- Transparency/semi-transparency plus dynamic high-contrast text
- Lower planes can affect color of higher translucent ones
- Full support for Unicode, including wide glyphs and bidirectional text
- Composed keys (number pad, etc.) are mapped into Private Supplementary Area B
- Image/video support via ffmpeg or OpenImageIO
- Subregion fade in/out
- Linear interpolation for coloring geometric objects
- Multiple blitters, rotation, and arbitrary scaling
The vast majority of functions draw to ncplane objects. A partial order (currently a total order) always exists over the planes. There is always at least one plane, the "standard plane". This plane cannot be resized, deleted, moved relative to the visible area, or reparented. Whenever notcurses updates its idea of the visible area's dimensions, it will resize the standard plane (references to the standard plane are not invalidated). Planes may otherwise be any size (invisible regions will not be rendered, and count only against memory), and can be moved to any position relative to the visible area. All planes, including the standard plane, can be freely moved along the z axis.
A render operation consists of two logical phases: generation of the rendered scene, and blitting this scene to the terminal (these two phases might actually be interleaved, streaming the output as it is rendered). All ncplanes are locked while generating the frame. Frame generation requires determining an extended grapheme cluster, foreground color, background color, and style for each cell of the physical terminal. Writing the scene requires synthesizing a set of UTF-8-encoded characters and escape codes appropriate for the terminal, and writing this sequence to the output.
Each cell can be rendered in isolation, though synthesis of the stream carries dependencies between cells.
Recall that there is a total ordering on the N ncplanes, and that the standard plane always exists, with geometry equal to the physical screen. Each cell of the physical screen is thus intersected by some totally ordered subset of planes P0, P1...Pi, where 0 < i ≤ N. At each cell, rendering starts at the topmost intersecting plane P0. The algorithm descends until either:
- it has locked in an extended grapheme cluster, and fore/background colors, or
- all i planes have been examined
At each plane P, we consider a cell C. This cell is the intersecting cell, unless that cell has no EGC. In that case, C is the plane's default cell.
- If we have not yet determined an EGC, and C has a non-zero EGC, use the EGC and style of C.
- If we have not yet locked in a foreground color, and C is not foreground-transparent, use the foreground color of C. If C is CELL_ALPHA_OPAQUE, lock the color in.
- If we have not yet locked in a foreground color, and C is not background-transparent, use the background color of C. If C is CELL_ALPHA_OPAQUE, lock the color in.
If the algorithm concludes without an EGC, the cell is rendered with no glyph and a default background. If the algorithm concludes without a color locked in, the color as computed thus far is used.
notcurses understands Unicode wide characters, and accounts for them. It is not possible to split the colors or styling of a wide glyph. It is not possible to print half of a glyph. It is not possible to print a narrow glyph over half of a wide glyph without obliterating the other half. These are all terminal emulator limitations.
Whether and how a given Unicode codepoint will be rendered depends almost entirely on font support. In general, with sufficient fonts, emoji and other pictographs will be properly rendered as expected. The Linux console has particularly limited fonts, and most characters beyond ASCII are not reliable in that environment. Certain Unicode glyphs are used by notcurses for drawing. Failure to render these glyphs reasonably will have a negative impact on notcurses functionality. Most important of these are the Box Drawing Characters, the Block Elements, and the Braille Patterns.
A wide character can be written at any offset within a row save the very last column. If a character (wide or narrow) exists in the right cell of a wide character, the original character will be destroyed. A narrow character can be written at any offset within a row. If a character (wide or narrow) is written onto the right cell of a wide character, that original character will be destroyed. It is thus possible for a single wide character to obliterate four columns' worth of glyphs: if two wide characters exist next to one another, and a new wide character is written over the right half of the first, both original glyphs will be obliterated. Likewise, if another (higher) plane bisects a wide glyph, the entire glyph is obliterated.
notcurses does not currently handle right-to-left text in any special way, but terminals often apply their own heuristics and stylings. Generally this means that a series of glyphs from right-to-left languages will be reversed in the terminal, but this will not be detectable by notcurses's reflective calls (e.g. ncplane_at_yx()).
Multiple blitters are provided, and can be selected whenever pixel data is being rendered. This includes ncvisual objects and qrcodes. If Notcurses is started in ASCII mode (as opposed to UTF-8), all blitters will degrade to NCBLITTER_1x1 (unless NCVISUAL_OPTION_NODEGRADE is provided).
|NCBLITTER_1x1||1x1->1||Uses spaces and sets the background color. The only blitter available in ASCII mode, and the only reliable blitter on the console. Pixel aspect ratio is equivalent to cell aspect ratio, usually resulting in vertical stretching. Lossless. Reliable no matter the font.|
|NCBLITTER_2x1||2x1->1||Default blitter. Pixel aspect ratio is one-half the cell aspect ratio, which is usually right where you want it. Uses Unicode upper- and lower-half blocks, and spaces. Lossless.|
|NCBLITTER_2x2||2x2->1||Pixel aspect ratio is equivalent to cell aspect ratio, usually resulting in vertical stretching. Uses Unicode quadrant and three-quarter blocks (in addition to upper- and lower-half blocks, and spaces). Lossy whenever more than two colors are used within a 2x2 pixel square, lossless otherwise (bi- and tri-linear interpolation is used for more than two colors).|
|NCBLITTER_3x2||3x2->1||Highest quality for most large images. Pixel aspect ratio improves over NCBLITTER_2x2 but is less perfect than NCBLITTER_2x1, leading to slight vertical stretching. Uses Unicode sextants, left and right half blocks, and spaces). Lossy whenever more than two colors are used within a 3x2 pixel square, lossless otherwise (generalized linear interpolation is used for more than two colors).|
|NCBLITTER_4x2||4x2->1||Uses Braille characters, which have spotty font support.|
|NCBLITTER_PIXEL||6x1->1||Pixel blitter (see below)|
Some terminals support pixel graphics, including the Sixel system pioneered by DEC. Notcurses can employ pixel graphics using the NCBLIT_PIXEL blitter.
- Sixel: xterm, mlterm, VTE, Alacritty (outstanding patch), Windows Terminal
- Kitty supports its own method
- as does ITerm2
Notcurses does not currently output ReGIS vector graphics.
Notcurses embeds a single pixel bitmap into a single cell as one (very) large EGC. This cell anchors the upper left origin of the bitmap. After emitting the bitmap, having some arbitrary size, the virtual cursor is forcefully repositioned to the right of the bitmap, on the row on which it started.
Notcurses provides input from keyboards and mice. Single Unicode codepoints are received from the keyboard, directly encoded as char32_ts. The input system must deal with numerous keyboard signals which do not map to Unicode code points. This includes the keypad arrows and function keys. These "synthesized" codepoints are enumerated in notcurses.h, and mapped into the Supplementary Private Use Area-B (U+100000..U+10FFFD). Mouse button events are similarly mapped into the SPUA-B.
All events carry a ncinput structure with them. For mouse events, the x and y coordinates are reported within this struct. For all events, modifiers (e.g. "Alt") are carried as bools in this struct.
It is not obvious what "transparency" or "alpha blending" means in a character context. I have assigned my own meanings. Each of the foreground and background channel of an ncplane's cell have two bits dedicated to alpha. Channels are always initialized to 0, and thus the default alpha setting is CELL_ALPHA_OPAQUE. It is important to note that glyph selection is independent of alpha. The first glyph found while descending the planes intersecting a cell will be the glyph used. Only presentation of the glyph is modified by alpha.
|00||CELL_ALPHA_OPAQUE||Use the fg color unchanged.||Use the bg color unchanged.|
|01||CELL_ALPHA_BLEND||Blend the fg color down.||Blend the bg color down.|
|10||CELL_ALPHA_TRANSPARENT||Select the next fg color.||Select the next bg color.|
|11||CELL_ALPHA_HIGHCONTRAST||Complement bg color computed through this plane.||Forbidden.|
The value 11 is currently forbidden for a bg alpha setting, but might be used in the future. To "blend the color down" means to average the colors encountered until hitting an opaque channel, or running out of planes. To "select the next color" means to ignore this color, and instead take the color as computed by lower planes.
High-contrast text is not strictly defined. notcurses will attempt to make the glyph as readable as possible, given the background color computed at the cell.
If loaded multimedia supports transparency (e.g. PNGs), transparent pixels will be considered as if CELL_ALPHA_TRANSPARENT was used.
Transparency plus bitmaps yield sprites. The "luigi" demo uses three bitmaps from Luigi's walking cycle in Super Mario Bros. Only one is shown at a time; the other two are hidden under the standard plane (onto which a background has been rendered).
notcurses can color lines via linear interpolation between the two endpoints. This is done with ncplane_hline_interp() and ncplane_vline_interp(). If provided two endpoints of the same color, the line will be that single color.
More information is available from the source tree in TERMINALS.md.
The two primary environmental factors affecting notcurses performance are the terminal emulator and the configured fonts.
For performance evaluation, I run notcurses-demo in each terminal three times. Each terminal is configured to use Inconsolata Medium 12 as its primary font, to 70% opacity (if supported), and run at a 70x80 geometry. I report the average of the three wall clock times, and the three FPS (i.e. frames rendered divided by time spent within notcurses_render()) measurements. If DirectColor output could not be rendered, the terminal is reported as a failure (this is perhaps/probably due to my ignorance). Some demos are a fixed number of frames, with a fixed target time. Some are a fixed number of frames, to be rendered as quickly as possible. Some are fixed time, with an intention of rendering as many frames as possible.
For the FPS measurement, higher is better. For the time measurement, lower is better.
FPS / Seconds
|11.87||196.8||xterm-direct||eagle and view were very choppy
widecolor doesn't colorize flame emoji
uniblock ran without box breakage (only terminal to do so)
xfce4-terminal 0.8.8 / vte 0.58.2
|682.3||72.9||kitty-direct||uniblock is deformed in a varying fashion
widecolor is missing some ranges
widecolor replaces some ranges with blocks
seems very smooth under load
|553.7||74.0||alacritty-direct||uniblock doesn't fade in properly||N|
(also VTE, but python)
terminator 1.91 / vte 0.58.2
konsole 19.08.1 / QT 5.12.5
|168.5||83.8||konsole-direct||uniblock doesn't fade in properly
uniblock persistent damage on one line
boldface seems particularly strong
Note: some of these terminals (e.g. xterm) export an RGB-capable setaf/setab, which notcurses does not use due to its special casing of low values. notcurses instead generates (for seta[bf] only) its own escapes outside of the terminfo framework. I am uncertain as to whether this might have performance effects. The "T.416" column indicates whether this terminal appears to support the colon-delimited RGB escapes from ITU T.416.
alacritty: 10140, 10121, 10143, 555.6, 553.8, 551.8, 1m13.9, 1m14.0, 1m14.1s konsole: 5655, 6286, 6433, 152.9, 174.3, 178.3, 1m24.3, 1m23.6, 1m23.5 terminator: 4628, 4788, 4759, 211.1, 208.6, 198.4, 1m15.1, 1m15.6, 1m16.5 kitty: 9475, 9539, 9518, 679.4, 687.5, 679.9, 1m12.9, 1m12.8, 1m12.9 xfce4-terminal: 4873, 4431, 4787, 214.7, 191.5, 211.4, 1m16.0, 1m16.1, 1m15.2 xterm: 1926, 1914, 1918, 11.8, 12.0, 11.8, 3m18.0, 3m14.7, 3m17.8
Notes on particular terminals
The TERMINALS.md document in Notcurses is (hopefully) well worth checking out.
- xterm, the first and (in many ways) the best.
- For 24-bit color, compile with --enable-direct-color and define the resource directColor to true. Both of these are the default in recent xterm.
- Use the xterm-direct terminfo entry
- For Sixel and Regis, compile with --enable-sixel-graphics --enable-regis-graphics
- VTE-based terminals including gnome-terminal and xfce4-terminal
- I'm not sure whether these ought be using the xterm- family or vte- family of terminfo entries, oddly enough
- screen: i've yet to see anything but a mess in screen
- tmux: i've only seen 256 colors work in tmux
The Linux "system console" is a virtual device mapping to some device. We're primarily interested in the VGA text console, and the framebuffer console. The console supports only 256 different glyphs (512 with diminished color support), and never more than 16 colors (8 with 512 glyphs).
You'll typically need to be a member of the video group to run fbterm. It offers much better Unicode glyph coverage than the raw console, but still offers only 16 (programmable) colors.
|3.0.0||not yet scheduled||Pixel plots|
|2.3.0||2021-05-09||Tree selector, tabbed interface, pixel blitting|
|2.2.0||2021-02-08||libreadline, progress bars, notcurses-core extraction|
|1.7.0||2020-08-30||Linux font table reprogramming, EGC inlining, better Rust wrappers|
|1.6.0||2020-07-04||True three-channel transparency (glyph, fg, bg), Quadblitter default, beefed up ncdirect|
|1.4.0||2020-05-10||Fdplane and subproc widgets, reader widget, true scrolling|
|1.3.0||2020-04-13||Multiselector widget, plot widget, multiline output, margins, staining|
|1.2.0||2020-02-17||Menu widget, selector widget, CELL_ALPHA_HIGHCONTRAST, Python/C++ wrappers|
|1.1.0||2020-01-19||Massive speedups and much better video support|
|1.0.0||2019-01-04||First GA release|
|0.9.0||2019-12-18||Recognize COLORTERM, damage map, quantized colors, _yx API extensions, alignment|
|0.4.0||2019-12-05||Cell API, input, resize handling|
|0.3.0||2019-12-02||Video support, transparent planes, fades|
|0.2.0||2019-12-02||Panelreels, image support|
|0.1.0||2019-11-30||Ncplanes, basic output|