commit 867b642a817ecdf7e35dfb31e37febc0904d3ec3 parent 95da4466bf95e6c68be8dde93d2b05d8a7c698a1 Author: lumidify <nobody@lumidify.org> Date: Sun, 12 Apr 2020 14:14:40 +0200 Add another note... Diffstat:
| M | NOTES | | | 10 | ++++++++++ |
1 file changed, 10 insertions(+), 0 deletions(-)
diff --git a/NOTES b/NOTES @@ -14,3 +14,13 @@ Ideas for text editor: https://en.wikipedia.org/wiki/Rope_(computer_science) https://en.wikipedia.org/wiki/Piece_table https://en.wikipedia.org/wiki/Gap_buffer +LtkTextLine should be abstracted out to be a generic +rope or gap buffer with the glyphs for the characters +also included at all times so they don't get out of +sync. The rendering function for LtkTextLine doesn't +need to know about shaping or anything - different +functions for actually rendering the glyphs just return +an abstract LtkTextLine that can be rendered without +caring about such details. This would easily allow +one file for shaping with harfbuzz, one for just +using the regular kerning with stb_truetype, etc.