-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[Feature] StaggeredLayout based on ItemsRepeater #3114
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
Comments
Thanks for submitting a new feature request! I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future! |
@DL444 @JustinXinLiu mentioned you had interest in working on this feature. Let us know. I know @skendrot had interest in this as well, so feel free to coordinate. |
@DL444 I'm currently in the process of converting all of the panels within the toolkit (WrapPanel and StaggeredPanel currently) to use the ItemsRepeater. It's not all roses on my side. This ItemsRepeater is taking some time learning how to work with it and there's no information out there except for the core **Layout source |
@skendrot I see. This is what I mean by "polishing". That code wasn't really tested for all situations. |
@DL444 I just added a bunch of random items
|
Thanks @skendrot for the updates! 🦙❤ I created a 7.0 branch. We should pull all the layout panels into their own package as a first step so we don't pull the WinUI dependency in for all the controls yet. Let me know if you need a hand creating the new project structure or not. |
Describe the problem this feature would solve
The current StaggeredPanel in this toolkit is based on Panel class, which doesn't offer UI virtualization. Memory consumption can go very high when a large amount of items are loaded.
Describe the solution
We could enable UI virtualization if we build a StaggeredLayout based on ItemsRepeater. This new control could have the same API as the existing StaggeredPanel.
Additional context & Screenshots
I've already built a prototype in-house. It still needs some polishing, but I hope to get it ready in the WinUI 3.0 timeframe. This should be in-line with 7.0 release plan #3062.
The text was updated successfully, but these errors were encountered: