[Bug 421] Implement a DIB engine

http://bugs.winehq.org/show_bug.cgi?id=421

--- Comment #113 from Detlef Riekenberg   2009-02-07 05:46:15 ---
To repeat my opinion (See #52), using "winedib.drv" is the wrong direction.

We should use the DDI (Device Driver Interface) between GDI32 and
the Drivers (DDI can be used parallel to our old API).
For this, the DIB implementation must move to GDI32
(the GDI Rendering Engine: Eng* and friends).

That way, we have only one physdev, our code can decide, when to use
Driver rendering, OpenGL acellerated rendering or software rendering.

This direction is required, when we want to support native drivers.
For simple Workstations, this would be printer drivers.
For Workstations in a company, this includes also Mirror Drivers
(for remote control)
We could have other Driver next to winex11.drv very easy
(winesdl.drv anyone ?)