Re:Leveraging Rust and the GPU to render user interfaces at ...
by jcelerier on Thursday March 09, 2023 @09:04AM
(#35081250)
But when you do software rendering you don't need to redraw the entire frame buffer, just the parts that changed, which can be very small even at 8k - e.g. the box of a checkbox being switched
[ Parent
| on HN ]
Re:Leveraging Rust and the GPU to render user interfaces at ...
by ben-schaaf on Thursday March 09, 2023 @09:20AM
(#35081411)
Scrolling requires redrawing most if not the whole framebuffer.
Re:Leveraging Rust and the GPU to render user interfaces at ...
by HideousKojima on Thursday March 09, 2023 @10:56AM
(#35082585)
With scrolling couldn't you just shift the existing framebuffer up/down and only draw the newly scrolled-to parts?
Re:Leveraging Rust and the GPU to render user interfaces at ...
by kevingadd on Thursday March 09, 2023 @12:40PM
(#35084072)
The GPU buffering model doesn't usually let you read the previous frame like that these days, so you would need a scratch surface. That increases your bandwidth and memory requirements, so shifting doesn't end up being much faster if it's faster at all.
Re:Leveraging Rust and the GPU to render user interfaces at ...
by TylerE on Thursday March 09, 2023 @03:31PM
(#35086263)
I suspect there are enough edge cases (semi-transparent things jumps to mind) that it's unlikely to be lossless, anyway.
Re:Leveraging Rust and the GPU to render user interfaces at ...
by kllrnohj on Thursday March 09, 2023 @11:29AM
(#35083075)
You don't need to redraw the entire framebuffer with GPU rendering, either. It's perfectly possible to do small, partial updates.
See for example https://registry.khronos.org/EGL/extensions/EXT/EGL_EXT_buff...
And https://registry.khronos.org/EGL/extensions/KHR/EGL_KHR_part...