-
Notifications
You must be signed in to change notification settings - Fork 795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize refresh on remote server or slow network #32
Comments
Yes, we definitely have plans to improve this! No specific timeline at the moment, but optimizing rendering is a big one for us. What's your specific use case? Bubble Tea does have a high performance API for scrolling which the Viewport component can take advantage of (see I love your user icon, btw. |
@meowgorithm currently, bubbletea has HUGE troubles with rendering, honestly. when you try to update screen you have two ways: Way №1) use ansi codes in result of Way №2) rerender all app. But, emmm, you know, that's worst idea, we need avoid it. So. what's my solution: What if we replace |
I'd prefer not to introduce lower-level drawing commands just yet. Bubble Tea actually currently has some low-level scrolling commands for performance reasons, and they're much harder to work with compared to versus just describing a UI with One of the primary design goals in Bubble Tea was to remove the need for the user to worry about rendering logic. All that said we are exploring a notion of a more advanced, AST-based renderer where one can return a layout and the renderer repaints only things that have changed. |
flutter also allow users don't care about how widgets render, however even flutter have build context. i'll try to make a few solutions and come back |
Just a note that #95, which was merged about a week ago, contains an optimization where only changed lines are repainted. We have further optimizations planned, but this should improve rendering over the network quite a bit. |
Just a datapoint: #95 seems like it definitely helps! I was using Turning |
Hi old friends. I'm going to close this one as it's been several years and #95 has been pretty successful in our eyes. We do have further optimization planned, and have performed other optimizations since. If there are still relevant issues here please re-open. I'll also note that |
On the device with slow refresh rate, every "View()" will cause a blink since it re-renders the whole area or fullscreen. Do you have any plans to only re-render the the part it changes in order to avoid those blinks? (just like Kindle devices, not every page-up/page-down will cause a whole refresh)
The text was updated successfully, but these errors were encountered: