Migrate WinForms to Avalonia

[IsaacMarovitz]

By switching to Avalonia, platforms other than Windows can be supported. I would love to work on this but I would be interested in hearing the maintainers' opinions before undertaking it.

[ItsEasyActually]

This requires a genuine proposal and many things to happen before it even can be considered in my opinion. The tools (the libraries we have really) need overhauls if we do anything this monumental, and it would be ideal to rewrite (and decouple) the existing libraries first. I do not believe the UI should be anyone's focus point until we have a plan for fixing up underlying issues on the libraries.

Additionally, there is an in progress Avalonia theme for this org in development for the Mod Managers (repo not available yet). I want it used for an eventual rewrite of the UI on this tool suite, but again, there are a lot of other things that need to be done first.

[IsaacMarovitz]

This requires a genuine proposal and many things to happen before it even can be considered in my opinion.

That's understandable, when I looked through I definitely saw places in need of improvement. Could we keep this open for the sake of tracking?

[PiKeyAr]

Recently I came across the Eto framework (https://github.com/picoe/Eto) which provides a multi-platform solution but is less complex to deal with than Avalonia (I think?). Might be worth looking into converting from pure WinForms to this.

[IsaacMarovitz]

Recently I came across the Eto framework (https://github.com/picoe/Eto) which provides a multi-platform solution but is less complex to deal with than Avalonia (I think?). Might be worth looking into converting from pure WinForms to this.

I'm not a fan of this using MonoMac. This also seems to be targeting older versions of .NET