Having been a long time linux user and a follower of the Wine project, there are a couple of things that stand out to me that may help with some long-running problems.
As Wine is in pretty active development, several bugs are closed and many new ones opened which affect a large number of apps, and in the CXGames users interests, affect games. One thing of note is that often times there are certain builds of Wine which work almost perfectly with a particualr game in version X of Wine, but is broken in version Y.
One recent example of this is the game "Sins of a Solar Empire" (APPDB entry at http://appdb.winehq.org/objectManager.php?sClass=application&iId=6653) which had issues but was semi-playable on version 0.9.60 but the installer broke post 1.0. This may not be the best example, but is just one of many examples of this type of issue.
This issue likely creeps up in CXGames, and installing the new unsupported builds may help some games, but break others.
This being the case, what is the potential for being able to have the CXGames front-end utilize multiple Wine/CXGames backend versions to support apps in particular bottles? If it is discovered that Game "A" works better with version "X" of a CXGames backend, would it be possible to launch and use that game using version "X", while using version "Y" for other games?
If that were the case, what about using the "official" Wine versions, but managed by the CXGames frontend?
I know that this type of functionality would represent one of the greatest value-add propositions for me when it comes to unsupported software. CXOffice and CXGames are excellent products for running supported software, but when dealing with unsupported software results can be hit and miss. Instead of having to resort to standard Wine versions installed stand-alone and used via command-line to try for better compatibility, perhaps allow them access to those options while maintaining the simplicity and ease of the GUI.
