http://bugs.winehq.org/show_bug.cgi?id=19376
--- Comment #7 from Lucas Murray lmurray@undefinedfire.com 2009-07-19 20:57:25 --- (In reply to comment #6)
If that's what you want, sure it can be implemented. Of course a better way would be fixing kwin's compositing...
It's not KWin's compositing that's the problem, it's both the compositing idea in general and the quality of the graphics drivers that are currently available to us.
When compositing is enabled there will ALWAYS be a speed penalty due to the extra redirection that needs to be done and it doesn't matter how fast the graphics card is or how well the driver is optimized it will always be the case. This is the primary reason why those DWM calls exist.
On Linux we have an extra problem: Our graphics drivers have not been optimized as far as humanly possible unlike those on other operating systems. Due to this when compositing is enabled we get both a larger performance hit and redirection problems such as those found in the KDE/Compiz trackers.
As the window manager has no way of knowing if an application is running a 3D context and as graphics drivers will take a very long time to fix completely implementing this in WINE will allow the user to easily get faster applications without the need of externally writing scripts for every single one.