[Feat] Auto Download Wine if no version was found in the system

[flavioislima]

Description

This is the first feature I get from HyperPlay, this is the original PR:
HyperPlay-Gaming/hyperplay-desktop-client#317

It basically checks if there is any Wine/Proton/Crossover available, or at least that it could found, if none was found it downloads the latest Wine-GE on Linux or the latest Wine-Crossover on macOS.
We wanted to implement this in Heroic but I decided to do it first in HyperPlay to check how we could get features and fixes from the fork.

The download happens during startup just like DXVK or when launching a game.
Since most version are around 80 to 100MB I think that should be fine for most people for now, but we can improve this after getting more feedback.

I also think this won't affect anyone on the Steam Deck or that uses Steam on linux to play.
It will affect more people on macOS that does not know what Wine or Crossover are and wants to just download and play a Windows game there.

It also fixes an issue on macOS that was causing games to fail to launch due to not finding the wine prefix.
Also changes the name of the Wine Manager to Compatibility Layer, since it also covers Proton that is not Wine itself.
Might also be a more friendly name.

How to Test

To test this just make sure you rename all folders that have wine on your system like .steam, lutris folder, heroic/tools folder, etc. And check if Heroic will download the correct version on Startup and show it on the Compatibility layer screen.

---

Use the following Checklist if you have changed something on the Backend or Frontend:

• Tested the feature and it's working on a current and clean install.
• Tested the main App features and they are still working on a current and clean install. (Login, Install, Play, Uninstall, Move games, etc.)
• Created / Updated Tests (If necessary)
• Created / Updated documentation (If necessary)

[CommandMC]

Also changes the name of the Wine Manager to Compatibility Layer, since it also covers Proton that is not Wine itself.

I'm not a huge fan of this, since "Compatibility" could mean anything (for example, https://github.com/luxtorpeda-dev/luxtorpeda and https://github.com/dreamer/boxtron are also "Compatibility tools").
Yes, Proton isn't Wine, but if you'd want to be correct about this everywhere, you'd have to rename a bunch of other things as well ("Wine Version" -> "Compatibility Tool Version" (?), "Wineprefix", etc.)

[imLinguin]

we might use Luxtorpeda eventually though

[flavioislima]

Also changes the name of the Wine Manager to Compatibility Layer, since it also covers Proton that is not Wine itself.

I'm not a huge fan of this, since "Compatibility" could mean anything (for example, https://github.com/luxtorpeda-dev/luxtorpeda and https://github.com/dreamer/boxtron are also "Compatibility tools"). Yes, Proton isn't Wine, but if you'd want to be correct about this everywhere, you'd have to rename a bunch of other things as well ("Wine Version" -> "Compatibility Tool Version" (?), "Wineprefix", etc.)

Yes, the thing is that we can also add more stuff there in the future like @imLinguin said.
I did not want to change everywhere at first but I can change other places now if you think its better. For me I am good with it

[CommandMC]

We can of course add other compatibility layers later, that wasn't what I was saying.
I see two potential issues with "Compatibility Layer":

• Users unfamiliar with Heroic don't immediately know what it does (with Wine Manger, you could at least Google Search for Wine & you'd know what it is)
• Users familiar with Heroic might expect this "new" Compatibility Layer tab to be able to do more than just manage Wine(/Proton/CrossOver), which it of course currently can't

If we do ever end up adding something like Luxtorpeda, then I'd say Compatibility Layer is a fine name. For now, it's IMO just imprecise for no reason

[CommandMC]

Sidenote: The name itself is also a little confusing. With it being named "Compatibility Layer", you'd think you can configure one Compatibility Layer, but instead you can install/update/remove different ones. IMO a "Manager" should be in there somewhere (but "Compatibility Layer Manager" is a little long)

[arielj]

what do you think if we just do Wine/Proton on linux and Wine/Crossover on mac as the term?

Like Use default Wine/Proton settings Wine/Proton Manager, etc. It makes it super obvious and it's in length between wine and compatibility layer.

I do feel that we should add more content at the top of that section to explain it a bit more, maybe link to some wiki page for example. I think that it doesn't matter that much which name we pick if we allow users to easily find what it does when they enter that section.

[arielj]

One thing to add also is that there's another PR turning the Wine Manager section into a Tools Manager section that also would cover things like DXVK/VKD3D. Maybe Tools manager is more generic.

[flavioislima]

Ok, since this discussion can take too long and we don't have any type of metric to use to decide, I will just revert the naming change.
Take a look at the rest of the PR once you guys have the time.

[CommandMC]

LGTM from the code, but I haven't had the time to properly test this yet