Multiplatform UI

[Kebechet]

Is your feature request related to a problem? Please describe.
The main problem of current ResXManager is that it is done in WPF and thus it is not multiplatform. Like mentioned in following tickets:
#53
#381

Describe the solution you'd like
From my PoV it would be most beneficial to rewrite the UI into Blazor and also fix potential Windows-only dependencies with some multiplatform ones. Why Blazor ? Because then you could just import a blazor component into e.g. you private admin panel page or embed it theoretically into anything.

Questions for community
Would community appreciate such rewrite ?
Do you see there any potential problems ?
Would there be a better solution like the one I provided to allow the best reusability ?

[bdovaz]

@Kebechet isn't it better to use MAUI? It would be easier to do the refactoring no doubt since it is still in xaml (although slightly different), there are still the concepts of converters, etc...

And easier for all contributors not to have to learn a technology so different from WPF, MAUI is quite similar.

cc: @tom-englert

[Kebechet]

@bdovaz depends. It would be easier to rewrite to MAUI for sure. But benefits of web are much greater. E.g. to inject it as a standalone component into your CRM and use it for managing languages.

But this task would take a lot of time. And I doubt someone will go for it. If I am not that busy I would do it myself.

[bdovaz]

@Kebechet integrating it as a component of Blazor I see it as something separate because surely you do not want to see the UI as it looks or that certain features do not make sense as is in web environment.

I see clear the port to MAUI and in the future little by little, port certain XAML views to Blazor to be able to share it in desktop and web environment at the same time.

[tom-englert]

You're aware that the VisualStudio extension is the main use case? I doubt it will run with something else than WPF on NetFramework.