Ove Kaaven <[EMAIL PROTECTED]> writes:
> I've been thinking about going about all this in a different way. Instead
> of loading up dlls/ddraw with driver-dependent code, perhaps we should
> consider driver separation not only in dsound (like it's done now, with
> IDsDriver in the wineoss driver), and like I want to do with dinput
> (IDiDriver in winmm's joystick driver etc), but also in ddraw?
>
> So the x11drv (and any future graphics drivers) would export a
> IDdDriver-or-whatever-it's-called COM interface, that dlls/ddraw could
> then build upon, just like in windoze. All the DGA, DXGrab, and GLX code
> would then have to be moved into the x11drv, obviously, so it'd be a lot
> of work, but it'd certainly give us some advantages as well...
If there are defined COM interfaces that allow doing this, then yes
that would definitely be a good thing.
OTOH if it involves defining a new ad-hoc driver interface that just
moves things around but doesn't abstract anything (see WND_DRIVER for
an example of how not to do it), then it's worse than doing X calls
directly.
I don't know enough about ddraw to say which case it would be; if you
have some time, could you try to come up with a list of the services
you'd need the x11drv to export for this to work?
--
Alexandre Julliard
[EMAIL PROTECTED]
