Ledit: Simple, GPU-rendered, no bullshit text editor

Re:Ledit: Simple, GPU-rendered, no bullshit text editor by chrisseaton on Wednesday February 23, 2022 @07:29PM (#30448729)

Don't all serious desktop environment render glyphs using the GPU anyway? So don't you get that for free when you use the standard frameworks?

[ Parent | on HN ]

Re:Ledit: Simple, GPU-rendered, no bullshit text editor by floatboth on Wednesday February 23, 2022 @09:11PM (#30449465)

Gtk4 and QML sure do (QML still (?) uses SDFs, Gtk4 uses atlas textures like WebRender does). Older frameworks don't.

[ Parent | on HN ]

Re:Ledit: Simple, GPU-rendered, no bullshit text editor by jcelerier on Thursday February 24, 2022 @03:29AM (#30452245)

The default in QML used to be atlases, you can revert back to them with the following:

    renderType: Text.NativeRendering

or:

   QQuickWindow::setTextRenderType

[ Parent | on HN ]

Re:Ledit: Simple, GPU-rendered, no bullshit text editor by myfavoritedog on Wednesday February 23, 2022 @07:48PM (#30448900)

Standard frameworks give you text frames with minimal hooks to customize them and "good enough" performance. They're great for dumping a log file to or for small documents, but when you want the fine control of a text editor that can handle big files, you need to roll your own.

[ Parent | on HN ]

Re:Ledit: Simple, GPU-rendered, no bullshit text editor by kazinator on Wednesday February 23, 2022 @08:01PM (#30449002)

GPU acceleration of the text editing viewport, which will not show much more than 100 lines of text at any time, has almost nothing to do with the issues in editing large files.

[ Parent | on HN ]