Using ListDetailsView from Community Toolkit?

[suchja]

@XamlBrewer Maybe you get this twice, but I'm not sure whether my comment on the blogs really works.

Really nice article. Thank you! Finally a piece which works out of the box. In the WinUI3 realm this is really rare.
Maybe I missed something, but why did you NOT leverage the ListDetailsView from Windows Community Toolkit?

[XamlBrewer]

@suchja Great question! I indeed considered migrating the Windows Community Toolkit ListDetailsView from UWP to WinUI 3. But there were not enough overlapping features:

• ListDetailsView in Compact mode shows List OR Details, I always want to show both.
• ListDetailsView has multi-screen support, which I'm not interested in (and I also don't wanted to migrate the underlying TwoPaneView)
• ListDetailsView has no out-of-the-box support for interaction with the command bar on top and the inline command bars in the list elements. This is a key feature that I wanted in my own MasterDetail scenario.

Therefor I decided to start from scratch.

[suchja]

@XamlBrewer Thanks a lot for your immediate feedback! That makes a lot of sense to me. One thing that is not clear to me is your statement:

I indeed considered migrating the Windows Community Toolkit ListDetailsView from UWP to WinUI 3.

The Windows Community Toolkit ships in a WinUI 3 version (including the ListDetailsView). When you say you considered migrating, is there some migration needed? I'm not really into UWP and still learning WinUI 3. However, I just searched the Windows Community Toolkit Repository and several articles and got the impression, that the WinUI 3 version of the WCT is independent from UWP.

I know this question is not really related to your great work here on your example. So thanks again for all the time and love you invest into your open source work!!! Is there any way to support your work?

[XamlBrewer]

@suchja At the time when I wrote the code, the WinUI3 version of Community Toolkit had dependencies to UWP libraries (via the Reunion packages). It was then not possible to create a WinUI 3 desktop app for .NET 5 or .NET 6. I'm not sure if that is still the case, but I wouldn't be surprised.