🧪 [Experiment] SizerBase class for GridSplitter + ContentSizer + PropertySizer

[michael-hawker]

Approved Discussion #96

Tracking Issue #101

Initial Commit of Experiment

This PR adds:

• SizerBase an abstract base class to centralize logic around input, visuals, and accessibility.
• GridSplitter knows how to manipulate a Grid's rows/columns
• ContentSizer knows how to manipulate the Width/Height of any FrameworkElement
• PropertySizer knows how to directly manipulate any bound double value
• Initial docs/samples for these components
• Tested manually and working on UWP/WinUI 3/WASM with no issues.
• Small fix for WASM loading files in root of sample projects
• Update to WinUI 3 version to help test on latest: Can't set ProtectedCursor in DependencyProperty PropertyChangedCallback - Access Violation microsoft/microsoft-ui-xaml#7062 (workaround is in this code, so no crash now here for us)

I'd like to finish before merging:

• GridSplitter examples

[michael-hawker]

Hmm, looks like I need to update the .NET version somewhere:

"D:\a\Labs-Windows\Labs-Windows\Toolkit.Labs.All.sln" (default target) (1:2) ->
"D:\a\Labs-Windows\Labs-Windows\tests\CommunityToolkit.Labs.UnitTests.WinAppSdk\CommunityToolkit.Labs.UnitTests.WinAppSdk.csproj" (default target) (15:6) ->
(WindowsAppSDKVerifyWinrtRuntimeVersion target) -> 
  C:\Users\runneradmin\.nuget\packages\microsoft.windowsappsdk\1.1.0-preview3\buildTransitive\Microsoft.WindowsAppSDK.targets(34,9): error : This version of WindowsAppSDK requires WinRT.Runtime.dll version 1.6 or greater. [D:\a\Labs-Windows\Labs-Windows\tests\CommunityToolkit.Labs.UnitTests.WinAppSdk\CommunityToolkit.Labs.UnitTests.WinAppSdk.csproj]
C:\Users\runneradmin\.nuget\packages\microsoft.windowsappsdk\1.1.0-preview3\buildTransitive\Microsoft.WindowsAppSDK.targets(34,9): error :     Please update to .NET SDK 6.0.104, 6.0.202, 5.0.213 or 5.0.407 (or later). [D:\a\Labs-Windows\Labs-Windows\tests\CommunityToolkit.Labs.UnitTests.WinAppSdk\CommunityToolkit.Labs.UnitTests.WinAppSdk.csproj]
C:\Users\runneradmin\.nuget\packages\microsoft.windowsappsdk\1.1.0-preview3\buildTransitive\Microsoft.WindowsAppSDK.targets(34,9): error :     Or add a temporary Microsoft.Windows.SDK.NET.Ref reference of version 10.0.*.24 or later. [D:\a\Labs-Windows\Labs-Windows\tests\CommunityToolkit.Labs.UnitTests.WinAppSdk\CommunityToolkit.Labs.UnitTests.WinAppSdk.csproj]
C:\Users\runneradmin\.nuget\packages\microsoft.windowsappsdk\1.1.0-preview3\buildTransitive\Microsoft.WindowsAppSDK.targets(34,9): error :     For example, [D:\a\Labs-Windows\Labs-Windows\tests\CommunityToolkit.Labs.UnitTests.WinAppSdk\CommunityToolkit.Labs.UnitTests.WinAppSdk.csproj]
C:\Users\runneradmin\.nuget\packages\microsoft.windowsappsdk\1.1.0-preview3\buildTransitive\Microsoft.WindowsAppSDK.targets(34,9): error :         <PropertyGroup> [D:\a\Labs-Windows\Labs-Windows\tests\CommunityToolkit.Labs.UnitTests.WinAppSdk\CommunityToolkit.Labs.UnitTests.WinAppSdk.csproj]
C:\Users\runneradmin\.nuget\packages\microsoft.windowsappsdk\1.1.0-preview3\buildTransitive\Microsoft.WindowsAppSDK.targets(34,9): error :             <WindowsSdkPackageVersion>10.0.<Target Windows SDK Build Number>.24</WindowsSdkPackageVersion> [D:\a\Labs-Windows\Labs-Windows\tests\CommunityToolkit.Labs.UnitTests.WinAppSdk\CommunityToolkit.Labs.UnitTests.WinAppSdk.csproj]
C:\Users\runneradmin\.nuget\packages\microsoft.windowsappsdk\1.1.0-preview3\buildTransitive\Microsoft.WindowsAppSDK.targets(34,9): error :         </PropertyGroup> [D:\a\Labs-Windows\Labs-Windows\tests\CommunityToolkit.Labs.UnitTests.WinAppSdk\CommunityToolkit.Labs.UnitTests.WinAppSdk.csproj]
C:\Users\runneradmin\.nuget\packages\microsoft.windowsappsdk\1.1.0-preview3\buildTransitive\Microsoft.WindowsAppSDK.targets(34,9): error :  [D:\a\Labs-Windows\Labs-Windows\tests\CommunityToolkit.Labs.UnitTests.WinAppSdk\CommunityToolkit.Labs.UnitTests.WinAppSdk.csproj]

Will look on Monday

[michael-hawker]

Should have all uno guards in place now. Glad they show up in the CI, that's pretty cool.

Main issue is we're getting some other internal uno error message about __storeBackingField from the DependencyObject generator. Following up with Uno team. Couldn't reproduce in a new Uno project copying our code over.

[michael-hawker]

Added ProjectTemplateRns to the <RootNamespace> tags for the source/library projects. that did work around #110 and cause the linux CI to pass. 🎉

Think it's fine for a workaround for now, we just want to validate new experiments don't keep that in the namespaces used in the code files during PRs until the underlying Uno issue is fixed and we can go back to using the same root namespace for everything.

[michael-hawker]

Woot! We have a clean build. Think this is all set to review @mrlacey and @Arlodotexe. (Outside of #116 and GridSplitter examples). Let me know if we want that fixed here first or as a separate PR. Would be nice to get a 2nd experiment in main though.

[mrlacey]

Approving on the basis that this gets a second experiment into the codebase.
However, this will be affected by #116 and #120

[michael-hawker]

Chatted with Arlo, so this isn't modifying the code that is causing #116 and #120 (and just exposing it). Let's merge this and our other open PRs to get all back together on our open work, and then take a look at fixing things forward.