C# Declared Styles/Resources?

[najak3d]

This is a crude brainstorm, from an Avalonia noob.

As I'm wading my way through the Default/Fluent Style AXAML's, and learning more about how all this works, and as I look at the AXAML for declaring styles, I can't help but note the long-strings with repetitive portions of each string such as:

    <StaticResource x:Key="RadioButtonForeground" ResourceKey="SystemControlForegroundBaseHighBrush" />
    <StaticResource x:Key="RadioButtonForegroundPointerOver" ResourceKey="SystemControlForegroundBaseHighBrush" />
    <StaticResource x:Key="RadioButtonForegroundPressed" ResourceKey="SystemControlForegroundBaseHighBrush" />
    <StaticResource x:Key="RadioButtonForegroundDisabled" ResourceKey="SystemControlDisabledBaseMediumLowBrush" />
    <StaticResource x:Key="RadioButtonBackground" ResourceKey="SystemControlTransparentBrush" />
    <StaticResource x:Key="RadioButtonBackgroundPointerOver" ResourceKey="SystemControlTransparentBrush" />
    <StaticResource x:Key="RadioButtonBackgroundPressed" ResourceKey="SystemControlTransparentBrush" />
    <StaticResource x:Key="RadioButtonBackgroundDisabled" ResourceKey="SystemControlTransparentBrush" />

Would it be a feasible concept to convert this to C# notation? I would picture a style being a set by C# classes, and even permit overrides, so that styles could inherit/polymorph from other styles in a C# fashion. Of course it would also permit the inclusion of arbitrary children to add to it's collection of Resources (or override existing ones).

Then the implicit AXAML based ResourceKeys would use Class Name as part of the key name with "dot-notation" such as:

 <Panel Background="RadioButton.Background"  />

And then in C#, if you were using Markup.Declarative plugin for your UI composition, to reference a Resource, do this:

    new Panel()
         .Background(Styles.RadioButton.Background)

And thus would look the same in C# vs. AXAML.

Targeted benefits I have in mind are:

1. Clearer user-code that allows intellisense to work with Styling/Resources in VStudio, VCode, and Rider alike.
2. Faster compilation, and fewer dynamically compiled styles.
3. Easier to understand Avalonia source code. Stack traces don't result in taking you to dynamically compiled code.
4. C# and AXAML notations for accessing Styles/Resources would be Equivalent.

My Current Perceived Issues:

1. Forcing clients to use "Rider + Plugin" for good experience is a sizable/prohibiting pill-to-swallow.
2. Tedious/long/repetitive strings. Fragile?
3. No clear way to use C# declarative methods for accessing styles/resources as is done in AXAML. (I might be missing something!)