http://bugs.winehq.org/show_bug.cgi?id=421
--- Comment #67 from max@veneto.com 2008-11-03 13:02:29 --- (In reply to comment #66)
(In reply to comment #65)
(In reply to comment #63)
Looks like Autocad might need this; see bug 13801.
I guess you're right, as most time is spent calling DIB_Coerce stuffs.
It would too difficult to drop a DIB engine skeleton with calls to actual graphic engine, so people can start to look at it in a consistent manner ? I've seen many proposals in years, but still nothing in wine tree.
I can understand that DIB engine should be carefully (and slowly) introduced in wine, but without a proper starting point it'll never happen.
It's already ready being worked on by Huw, and it's not something that can be gradually introduced.
from http://www.winehq.org/pipermail/wine-devel/2006-April/046786.html :
"Alexandre has very specific ideas about how he wants a DIB Engine done.
"Integrating a DIB engine into your own tree may not be too difficult. The hard part is integrating it into the Wine tree in small pieces without breaking everything else and keeping Alexandre happy as you go."
from WWN :
Huw Davis :
"I'm going to stop working on this for a while....." and "I'm not planning on doing any work on it for a while, but will probably return to it at some point in the future. "
Well, sorry but it seems to me that what you just said is exactly the opposite as the true situation.
Max
-
wine-bugs＠winehq.org