3 ms·
It's your app, so obviously do whatever you want, but I agree with the sibling comment that an immediate mode GUI wastes valuable CPU cycles redrawing the frame
by airstrike 2y ago
It's your app, so obviously do whatever you want, but I agree with the sibling comment that an immediate mode GUI wastes valuable CPU cycles redrawing the frame repeatedly and will invariably hurt performance
Again, since iced is "just rust", you can write whatever widgets you need, although it comes with a long list of built-in widgets (and there are many more built by the community). You can compose views with a bunch of these widgets to get to the UI you want.
There's also nothing stopping you from creating a way for users to write widgets for your iced application. The sky is the limit.
And I'm singling out iced because I'm a fan, but this should be true for pretty much all robust GUI toolkits out there.
- adastra22 2y agoIsn’t iced immediate mode?
- airstrike 2y agoNo, it's a bit of a mix. Retained until some update is processed by the runtime which causes the widget tree to be rebuilt, in which case it gets diff'd and stale widgets get replaced. Some widgets always redraw though, like Canvas, but they expose caching functionality I'm no authority here but that's the gist of my understanding