You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some software packages, like Microsoft Office, might come with different variants of the same program the user must choose before installing the package in question. Settings might be some such as the following:
Architecture
Language
Product tier ("Home", "Pro", etc)
Licensing ("Retail", "Volume", so on)
Bottles installers should thus be able to ask the user, in order to correctly prepare the installation process.
Two issues about implementation I can think of in particular:
UX, as there's many ways to ask users for install options. This could either be as simple and straighforward as showing dropdown lists with a GtkDropDown per option inside a GtkPopoverMenu when clicking the install button -- to showing custom, scripted dialogs a la Winetricks.
Static or dynamic implementation, that is, whenever each option is listed as its own program in the repo, or whenever one program YAML can receive parameters and configure the installation process based on them. Considering the complexity of having to update every single file and avoiding introducing new errors in the process in the static approach, I'm more inclined to the dynamic approach.
The text was updated successfully, but these errors were encountered:
Some software packages, like Microsoft Office, might come with different variants of the same program the user must choose before installing the package in question. Settings might be some such as the following:
Bottles installers should thus be able to ask the user, in order to correctly prepare the installation process.
Two issues about implementation I can think of in particular:
The text was updated successfully, but these errors were encountered: