Screenshots in this post are outdated, scroll to see the new ones.
[Update] How to test!
We have moved to Appimage for Bottles distribution!
To try the next Bottle experience, download here the Appimage, then make it executable:
chmod +x Bottles-commit-x86_64.AppImage
and run:
./Bottles-commit-x86_64.AppImage
Feel free to report bug and request new features here!
Concept
The new version (2.0) is designed from scratch and introduces a new concept based on environments.
In this version, the user is invited to create a maximum of 2 bottles (wineprefix):
optionaly a third:
Each bottle has its own preconfigured environment with specific characteristics.
Gaming environment
This environment has everything needed to run modern Windows games on Linux.
Enable DXVK/VKD3D and Esync by default. GL_SHADER cache is preconfigured and if there is more than one GPU (Optimus tech/Hybrid), the dedicated one is selected by default.
Optionally you can choose to use Proton instead of Wine. Through the integrated download manager, you can download a version of Proton or Proton-GE from GitHub and this can be used to create the new bottle.
This is a 64bit (or 32bit) prefix with Windows 10.
Software environment
This environment pre-installs libraries and frameworks commonly needed by Windows software to work best, for example:
- .Net Framework/Mono
- .Net Core
- C/C++/.. Redis.
- Fonts
and more.
This is a 64bit (or 32bit) prefix with Windows 10.
Runners management
Custom environment
Simply a basic wineprefix with no extras.
You can choose the Windows version and prefix arch (64/32).
Environments preferences
Although each environment offers different pre-configured settings, these are fully editable from the advanced settings of each bottle. This means that for example DXVK / VKD3D / Esync / .. dedicated GPU and more, can be configured in any bottle, regardless of the chosen environment.
System integration
From the file manager in use, by calling the context menu on an executable file (.exe or .msi) you can choose to start it (or install it) on an existing bottle.
Bottles
Each bottle offers the common tools (already available in previous versions of the software) to manage the system:
- management of installed applications
- winecfg
- winetricks
- debug
- CMD (and maybe Powershell)
- regedit
- backup
- Task manager
- reboot/poweroff
Backup and restore
There will be two methods of backing up a bottle:
- configuration file (maybe JSON)
- clone
In the first case, an instruction sheet is provided to reproduce the system (but not the installed software).
In the second case, a full backup of the bottle is created, including software. This can be imported into the software to make it usable as a bottle.
Development
I will work slowly on v2 but will keep the previous version updated.
You can see the development status in the develop branch.
Application preferences
From this version there will be the application settings (finally):
Confirmations
Any "harmful" action will have to be confirmed (as it should be):
First run helper
At start-up check that there is at least one runner, otherwise it recommends installing the latest version. (Without depending on system packages).