3 ms·
This basically fixes all of them by building a common umbrella that all existing UI toolkits (UWP, WPF, WinForms, Win32) can use. This picture summarizes it we
by Mistredo 6y ago
This basically fixes all of them by building a common umbrella that all existing UI toolkits (UWP, WPF, WinForms, Win32) can use.
This picture summarizes it well - https://github.com/microsoft/microsoft-ui-xaml/raw/master/docs/roadmap_winui3.png https://github.com/microsoft/microsoft-ui-xaml/raw/master/do...
- Ididntdothis 6y agoYou know the XKCD where they have 14 standards , create the a new one to unify them and the result is 15 standards?
- ptx 6y agoIt's the other way around, isn't it? They're not going to reimplement the Win32 API on top of WinUI, but WinUI uses Win32 in part for its implementation on some platforms (that platform being classic desktop Windows).
- SneakerXZ 6y agoWhat I meant was you can use WinUI 3 in your Win32 app, so it is a UI toolkit that can be used in any other existing UI toolkit.
- coribuci 6y ago> This basically fixes all of them by building a common umbrella that all existing UI toolkits (UWP, WPF, WinForms, Win32) can use. So intead of a screwdriver, a wrench or a hex key you have now a hammer.