4 ms·

Microsoft Fluent Design System was introduced in 2017. The homepage is useless, but the real docs are decent https://docs.microsoft.com/en-us/windows/uwp/desig

Microsoft Fluent Design System was introduced in 2017. The homepage is useless, but the real docs are decent https://docs.microsoft.com/en-us/windows/uwp/design/ https://docs.microsoft.com/en-us/windows/uwp/design/ Sadly, Microsoft still does not provide guidance or necessary APIs to desktop app developers (e.g. those primarily using .NET, Win32, WPF, WinForms, etc) to implement Fluent Design elements/controls. I'm hopeful we'll see a change here, but fear it'll happen too late, that is, before another design language is introduced.

WorldMaker 7y ago
> Sadly, Microsoft still does not provide guidance or necessary APIs to desktop app developers (e.g. those primarily using .NET, Win32, WPF, WinForms, etc) to implement Fluent Design elements/controls. I feel like the guidance is clear enough at this point: migrate to WinUI 3. If you can't migrate your app "all the way" to UWP today, you can use XAML Islands in Win32 apps and embed UWP/WinUI XAML in places that are appropriate. Some common WinUI controls that you might want to use have easy to find wrappers on NuGet to do most of the XAML Island magic for you for WPF and WinForms applications.
- withinrafael 7y ago
  That sounds great on paper but XAML Islands introduces insurmountable airspace issues. For example, you can't have a nice acrylic window--per Fluent design--and draw your existing WPF XAML on top. It's a non-starter in most cases. WinUI 3 has yet to be released. (It's only barely in alpha now.)
  - WorldMaker 7y ago
    > That sounds great on paper but XAML Islands introduces insurmountable airspace issues. For example, you can't have a nice acrylic window--per Fluent design--and draw your existing WPF XAML on top. It's a non-starter in most cases. If you are already using XAML, the WPF => UWP XAML transition shouldn't be so much of a hurdle as to be a "non-starter in most cases". In most Enterprise CRUD the biggest problem is DataGrid, but you pull one in from the Community Toolkit or one of the 3rd Party components vendors like Telerik. WinUI is talking about first party formally "Fluent" productizing the Community Toolkit's version sometime later in the 3.x timeline. Of course, my view of it is biased by doing a bunch of WPF <=> Silverlight XAML transition work by hand for a few years, and compared to that era, WPF <=> UWP is a lot more civilized. > WinUI 3 has yet to be released. (It's only barely in alpha now.) I forgot that part. Just replace WinUI 3 with WinUI 2 for "today" (up until 20H1, supposedly), and my statement stands.

WorldMaker 7y ago

> Sadly, Microsoft still does not provide guidance or necessary APIs to desktop app developers (e.g. those primarily using .NET, Win32, WPF, WinForms, etc) to implement Fluent Design elements/controls. I feel like the guidance is clear enough at this point: migrate to WinUI 3. If you can't migrate your app "all the way" to UWP today, you can use XAML Islands in Win32 apps and embed UWP/WinUI XAML in places that are appropriate. Some common WinUI controls that you might want to use have easy to find wrappers on NuGet to do most of the XAML Island magic for you for WPF and WinForms applications.

withinrafael 7y ago
That sounds great on paper but XAML Islands introduces insurmountable airspace issues. For example, you can't have a nice acrylic window--per Fluent design--and draw your existing WPF XAML on top. It's a non-starter in most cases. WinUI 3 has yet to be released. (It's only barely in alpha now.)
- WorldMaker 7y ago
  > That sounds great on paper but XAML Islands introduces insurmountable airspace issues. For example, you can't have a nice acrylic window--per Fluent design--and draw your existing WPF XAML on top. It's a non-starter in most cases. If you are already using XAML, the WPF => UWP XAML transition shouldn't be so much of a hurdle as to be a "non-starter in most cases". In most Enterprise CRUD the biggest problem is DataGrid, but you pull one in from the Community Toolkit or one of the 3rd Party components vendors like Telerik. WinUI is talking about first party formally "Fluent" productizing the Community Toolkit's version sometime later in the 3.x timeline. Of course, my view of it is biased by doing a bunch of WPF <=> Silverlight XAML transition work by hand for a few years, and compared to that era, WPF <=> UWP is a lot more civilized. > WinUI 3 has yet to be released. (It's only barely in alpha now.) I forgot that part. Just replace WinUI 3 with WinUI 2 for "today" (up until 20H1, supposedly), and my statement stands.