Skip to content
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

What is the best practice on a large amount of items in content? #29

Open
Masaokb opened this issue Nov 30, 2019 · 2 comments
Open

What is the best practice on a large amount of items in content? #29

Masaokb opened this issue Nov 30, 2019 · 2 comments

Comments

@Masaokb
Copy link

Masaokb commented Nov 30, 2019

I use StickyHeader to make iOS-TableView-like UI and add Column of my widgets StickyHeader's content.
But I suppose that the bigger the size of widgets, the less its rendering performance.
Is there any ways like ListView.builder, which render just visible widgets instead of all ones?

Maybe related to #3.

@sm2017
Copy link

sm2017 commented Apr 7, 2021

@Masaokb Do you have any solution?

@yasinarik
Copy link

When ListView.builder is used with shrinkWrap: true, it all loses the on-demand rendering feature. In the end, it performs very inefficiently. Because shrinkWrap wants the ListView.builder to calculate all the children even if they are not on the screen.

I have tried putting SliverList with SliverChildBuilderDelegate inside the content property of StickyHeaderBuilder. However, it gave this error:
A RenderStickyHeader expected a child of type RenderBox but received a child of type RenderSliverList.

So as of now, I also wonder how we can improve this package to allow it to render tens of thousands children efficiently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants