-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Unifiying MVVM and usage patterns #1083
Comments
Hey @crutkas, was just about to open an issue about this but I'll just comment here then 😄 I was browsing through the codebase today and saw you're already using some packages from the Windows Community Toolkit, have you considered moving Power Toys to use the new MVVM Toolkit (aka @michael-hawker and I will be happy to help if you have any questions about it! |
The other good thing with the MVVM Toolkit is that it's .NET Standard, so since Power Toys has WPF + UWP components, you could use it to help solidify the common bits between them (if any). |
We have chatted with @michael-hawker on this in the past and can see adopting this. While we want to do it, it is a larger task and would need each item broken down. I think don't think it is an item we are prioritizing for our larger 'push to stability' push but would accept community members helping migrate. |
Thanks @crutkas for the update. We should be shipping 7.0 in January 🤞. Would you be wanting to wait for our final release of the MVVM library or is getting started with the preview alright if someone wants to take this on? Our API surface for the MVVM Toolkit should be pretty stable now. I don't think we expect too many radical changes outside of potentially |
@michael-hawker Yup, outside of possibly some changes to In my branch for Preview 5 I mostly just have some more tweaks and minor improvements or internal optimizations, but nothing that would be breaking for consumers so far. |
a glorious dream but i doubt we'll ever get to a unified spot |
As we migrate work from existing frameworks in #891, we should start thinking about unifying our MVVM pattern frameworks.
MvvmLight comes to mind
The text was updated successfully, but these errors were encountered: