You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
apply UTF32 layout with true color support to terminal buffer (PR Utf32 buffer #1878)
cleanup intermediate CharData creation (part of PR Utf32 buffer #1878)
Idea is to move from the CharData based cell access to a more direct data access on the typed array. For convenience the CharData part could live on, but at least high throughput/runtime consumers (renderer and such) should be able to access the data in a faster more direct approach.
convert string based methods in InputHandler into typed array (covered by cleanup/enhancement of parser #1823)
This will save forth and back conversion of charcodes needed by the parser to "speak" with the string based API. (finally done by Parser hooks #2346).
eval other input encodings
In the future we might want to check, if we can gain anything from other input encodings (hottest candidate is UTF8, PR Utf8 input #1904).
Tracking issue to get outstanding core lib changes sorted:
CharData
creation (part of PR Utf32 buffer #1878)Idea is to move from the
CharData
based cell access to a more direct data access on the typed array. For convenience theCharData
part could live on, but at least high throughput/runtime consumers (renderer and such) should be able to access the data in a faster more direct approach.This needs some tweaks/refinement of the current attribute handling and will basically introduce a second 32bit value to be carried around.
InputHandler
into typed array (covered by cleanup/enhancement of parser #1823)This will save forth and back conversion of charcodes needed by the parser to "speak" with the string based API. (finally done by Parser hooks #2346).
fix the fullwidth problems in(seperately tracked Better handling of fullwidth chars #1779)InputHandler
In the future we might want to check, if we can gain anything from other input encodings (hottest candidate is UTF8, PR Utf8 input #1904).
The text was updated successfully, but these errors were encountered: