3 ms·
> how do I render as little as possible at a time, but also render everything/anything in the list "immediately" or as fast as possible. Isn’t that the constra
by setr 5y ago
> how do I render as little as possible at a time, but also render everything/anything in the list "immediately" or as fast as possible.
Isn’t that the constraint of basically any rendering system?
The html page itself — I want to only render what’s on screen, but still scroll down quickly
video games — I want to render only what’s in sight, but still turn quickly and render appropriately
Windows — I want to render the visible parts of opened apps, but still switch apps quickly
Etc
This isn’t fundamentally oppositional — it’s the most basic rendering optimization you’d apply (basically view culling), before getting into anything fancy
- lucideer 5y agoIt is exactly, and it's a hard problem to generalise. My point is that rendering a list widget is more complex than other widgets because it's as complex as general full-page rendering / scene rendering > This isn't fundamentally oppositional — it's the most basic... It can be both. View culling is essentially the complexity I'm talking about. View culling is a heuristic, it produces different impacts depending on many variables within the view, as well as the parameters of your cull.