Wine 1.6: This Year With These Interesting Features

[Artemis3]

<sarcasm>Kinda surprised that people tell free software projects what to do, rather than sit down and work on it themselves.</sarcasm>

The alternative, of course, is to hire people to do the changes you need.

[ryao]

<sarcasm>Kinda surprised that people tell free software projects what to do, rather than sit down and work on it themselves.</sarcasm>

Taunting aside, we're working on this. But we were told d3d10 is the über-most-important thing in 2008. It's 2013 now, and DX10/11-only games are still the exception rather than the rule(Battlefield 3 is the most requested one among them).

Re Steam: We are aware of this.

WINE is a difficult project to approach as an outsider. There is very little in terms of documentation available to enable new people to start implementing missing APIs. There also is not much documentation available on how one could debug when things go wrong. It would help both things greatly if there were high level description of the source code intended to get developers up to speed. It could be similar to the ZFS source tour:

http://hub.opensolaris.org/bin/view/...oup+zfs/source

Integration with DTrace could also help. DTrace would be useful both for understanding how the code works and for debugging issues.

Lastly, would Codeweavers implement support for DESTDIR in CrossOver's installer? That would make integration with Gentoo portage *MUCH* easier.