Replies: 8 comments 8 replies
-
|
i can for sure change that. |
Beta Was this translation helpful? Give feedback.
-
|
hmmm i dont know what to do with this. should i call Proton/Wine/DXVK compatibility tool and Proton-GE/Proton-CachyOS runner? i just want to have one way of calling things across the app before I push the update. |
Beta Was this translation helpful? Give feedback.
-
|
If we want a consistent naming convention, I suggest using "compatibility layer". |
Beta Was this translation helpful? Give feedback.
-
|
What about for Proton-GE and such? |
Beta Was this translation helpful? Give feedback.
-
|
I'm just proposing a change to the naming of the groups section in runners.json, suggesting a more semantically meaningful term to replace "groups." Everything else remains unchanged - |
Beta Was this translation helpful? Give feedback.
-
|
@nickexe Everything looks good on my side. |
Beta Was this translation helpful? Give feedback.
-
|
@nickexe The icons do not work in the Flatpak version and WineZGUI doesn't show up either. This is really stupid. |
Beta Was this translation helpful? Give feedback.
-
|
Closing since it's done. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
@Vysp3r
Just a quick naming suggestion — I noticed the top-level "groups" field in the runners.json structure.
Since it mainly holds collections of compatibility tools like Proton, Wine, DXVK, etc., maybe a more descriptive name like
compat_layersorcompat_toolscould help make the purpose a bit clearer?Totally up to you of course! I figured I'd bring it up now since the format hasn't been finalized or released yet, and it's always easier to make naming changes early on than later down the line.
Beta Was this translation helpful? Give feedback.
All reactions