[Feature] Make it easy to include Reactor element in existing XAML

[dotMorten]

Problem

There seem to be cases where XAML is a great use-case, and other cases where Reactor works great. There are also lots of existing XAML apps that could use an easy way to slowly transition towards Reactor. Having an easy way to create Reactor-based controls to host in XAML markup could be in interesting way to combine best of both worlds.

Proposed solution

One way this could be accomplished is by having a Reactor host-control, with a reference to the element you want to host by type. For example:

<Grid>
   <ReactorHostView Element="local:MyElement" />
<Grid>

Alternatives considered

Another approach could be to declare a control from code-behind that can be hosted in XAML. For example:

public class MyControl : ReactorControl
{
   public override Element Render()
   {
      return VStack(); 
   }
}

Additional context

No response

Confirmation

• I have searched existing issues and specs for prior discussion of this idea.

[mrlacey]

I much prefer the alternative suggestion here.
If using this, I'd want to not have to use a special host type for every element and "stringlytype" the actual class.

The only argument I can see for the user/developer for having a host element is to highlight the different underlying models.
I think I'd want to understand how the two could work together before making a final decision though

[dotMorten]

@mrlacey it wouldn't be stringly-typed parameter though. That's an actual type parameter, so if the type doesn't exist you'd get a compilation error and red squiqqles.
However there might be some issue with type parameters, since we'd need to create the type dynamically, which could cause AoT issues.