Prospecting MewUI controls ecology

[shonescript]

I am experienced in windowforms/wpf, knows some Win/Maui/Avalonia/Uno, but is tired with all these messy tech and trivial conversions.
Mew UI is concise and clear to me. I think it is the best lightweight .NET cross-platform UI, featuring an exceptionally excellent architecture with minimal dependencies and outstanding performance.
Althugh it is may be a personal project, but has potential with author rich UI experience and best AI vibe-coding behind. One day it will become a great MewUI control ecology.
A complete control ecology may require four levels:

Core control

• Base controls and infrastructrue authored by main code repository, focusing on core functions and performance, ensuring consistency and extensibility.
• Provide two pattern extensibility: inheritance and composition ability. Here suggest the author to open many ‘public 【sealed】 class XXXControl’ for a chance of later inheritance.

Inherited extension control

• Creating new controls/extension/system by directly inheriting from base control in fork project or third party project, focus on functionality and practical usability, ensuring users can easily use the controls based on past experience.

Composing user control

• Creating new controls/extension/system by composing base control or inherited control in fork project or third party project, also focus on functionality and usability.

Hosted or custom draw control

• Lots of controls could be imported through XXXHost or XXXDrawControl wrapper, focus on portability and interoperability.
  For example, when there is a WinformControlHost MewUI control, then all other winform controls can be directedly used in MewUI.
  Another example, when there is a SkiaCanvasControl or DrawingGraphicsControl, then many skia or drawing based controls can be ported through custom draw overriding.