robloo / publicdocs

Contains documents and articles that may be publicly useful.

| 中文 |

Contents

This repository contains documents and articles that may be publicly useful.

XAML UI-Frameworks

• XAML Framework Comparison : The most complete comparison of three major cross-platform XAML UI frameworks for .NET. This article includes a history of XAML frameworks, an at-a-glance comparison table, as well as detailed remarks explaining ratings.
• XAML Framework Controls : Lists available controls for several XAML framework excluding some primitives and shapes. It also describes some of the differences in implementation or usage where appropriate.
• Overview of WPF & UWP Differences : Lists major differences between WPF and UWP (which became WinUI 3). Microsoft does not provide any such list of differences which are considerable in some places.

Miscellaneous Topics

• AI-Driven Development : An idea for accelerated test-driven development using large-language model AI used in a supervised feedback loop.

publicdocs's Issues

Include Eto.Forms in comparison?

Would it be worthwhile to include Eto.Forms in your XAML Framework Comparison?

Extra properties for UWP Panel controls

The Panel controls in UWP like Grid, StackPanel, Canvas, RelativePanel, etc have some extra properties which in WPF are only in Border

• Border (Brush)
• BorderThickness
• Padding
• CornerRadius.

This makes Border "obsolete" and can be used to decrease the tree size.

Add Read-only DPs missing in UWP (along with it DependencyPropertyKey)

As titled

Any plans to update the information on Avalonia?

Specifically interested in updates for the license information.
We also now have VSCode support, although its in preview with our GitHub sponsors right now.

Add note on ThemeResource

Add Expander and InfoBar Controls once WinUI 2.5 is released

WPF does have the x:Uid directive

First of all, I would like to thank you for creating the overview of differences between WPF and UWP. It's a great idea because many people seems to think that because both are XAML based, they are very similar, when actually is quite the opposite.

Revising the table of differences, the first thing I found is that x:Uid doesn't exists in WPF, which is incorrect. There is already a x:Uid directive that can be used to localize WPF applications. The process may be cumbersome (generate CSV files, use LocBaml, etc.), but still is a way to create localizable WPF apps.

Regarding the topic of localization, an alternative to Uids in WPF is to use the DynamicResource extension, which seems to be missing in the comparison table.

Add details about inability to get control reference generated by template in UWP

https://docs.microsoft.com/en-us/dotnet/desktop/wpf/controls/how-to-find-controltemplate-generated-elements?view=netframeworkdesktop-4.8

Add new document comparing the main XAML frameworks (WPF, UWP, Avalonia, WinUI)

• Xamarin Forms / Maui and Silverlight are excluded for now
• Include graphic for history of the frameworks

UWP has a Tunneling Event after All

Adjust the event section to account for PreviewKeyDown

https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.uielement.previewkeydown?view=winrt-20348#remarks

x:Bind support in ControlTemplates was added after 1809

unoplatform/uno#4360

https://docs.microsoft.com/en-us/windows/uwp/xaml-platform/templatebinding-markup-extension#:~:text=Using%20x%3ABind%20in%20a%20ControlTemplate%20requires%20Windows%2010%2C,extension%20anywhere%20you%20use%20TemplateBinding%20in%20a%20ControlTemplate.

Add Comparison of Avalonia and Uno

Hi @robloo,
thanks for the very useful document. We could also add the comparison of Avalonia and Uno *.

The Avalonia comparision is just here.

Run benchmarks between avalonia, wpf and UWP/winui(uno) in different platforms

Run benchmarks between avalonia, wpf and UWP/winui(uno) in different platforms

See https://github.com/Noemata/XamlBenchmark