2021-06-06, 00:31
Thanks for the link, I haven’t looked at mono for a very long time.
I’m planning to move MMH from .NET Framework 4.8 (Windows only) to .NET Core 5/6 which is/will be supported on Win, MacOS and Linux. MMH uses a few .NET libraries including its UI which are supported in .NET Core 5 now and will be in upcoming .NET 6.
.NET Core 5 does not have a UI but I’ve already tried porting some non UI classes and although it’s not automatic, only a small amount of code needs changing (so far..)
.NET 6 is due for release in November and will have a UI (code named MAUI). Pre-releases due every month through to official release. MAUI info here: https://devblogs.microsoft.com/dotnet/in...rm-app-ui/
So my plan is to continue moving MMH to .NET 5 over next 3 or 4 months, releasing a .net 5 version when done (still Windows only) but ready for the .NET 6 November release.
Then when .NET 6 is stable I’ll start releasing MMH MacOS and Linux versions, initially with limited tools, over the following few weeks as alpha/betas.
Having said all that: I may have an immediate use for Mono, to role out a cutdown MacOS version with just a couple of tools for the MAC users over on QuadraphonicQuad forum... Unlike Kodi users, who are more tech savvy, many QQ’ers need a simple UI driven solution to do anything/everything. I get many more requests for MacOS than Linux on QQ, MacOS being perceived as a simpler environment by less tech savvies I think.
I’m planning to move MMH from .NET Framework 4.8 (Windows only) to .NET Core 5/6 which is/will be supported on Win, MacOS and Linux. MMH uses a few .NET libraries including its UI which are supported in .NET Core 5 now and will be in upcoming .NET 6.
.NET Core 5 does not have a UI but I’ve already tried porting some non UI classes and although it’s not automatic, only a small amount of code needs changing (so far..)
.NET 6 is due for release in November and will have a UI (code named MAUI). Pre-releases due every month through to official release. MAUI info here: https://devblogs.microsoft.com/dotnet/in...rm-app-ui/
So my plan is to continue moving MMH to .NET 5 over next 3 or 4 months, releasing a .net 5 version when done (still Windows only) but ready for the .NET 6 November release.
Then when .NET 6 is stable I’ll start releasing MMH MacOS and Linux versions, initially with limited tools, over the following few weeks as alpha/betas.
Having said all that: I may have an immediate use for Mono, to role out a cutdown MacOS version with just a couple of tools for the MAC users over on QuadraphonicQuad forum... Unlike Kodi users, who are more tech savvy, many QQ’ers need a simple UI driven solution to do anything/everything. I get many more requests for MacOS than Linux on QQ, MacOS being perceived as a simpler environment by less tech savvies I think.
