http://bugs.winehq.org/show_bug.cgi?id=421
--- Comment #427 from max@veneto.com 2011-08-06 15:58:56 CDT --- (In reply to comment #421)
(In reply to comment #420)
Won't patch to source for Wine 1.3.21
Please see http://www.winehq.org/pipermail/wine-patches/2011-April/100557.html . An engine written by Huw Davies has been under development in the main WINE tree since April. I don't know if Max's engine is still necessary; you may want to test with the latest WINE and roll back to the last known good version of this patch, since I don't know if the conflicting engines would cause problems or not.
I was quite surprised to see so little information divulged about such a major step for WINE. As we know from this bug, a DIB engine has been one of the most requested and longest-standing bugs in WINE, so for it to be merged essentially without commentary is a bit funny. I'd like to get perspectives from Max and others on the subject and on the engine that's being merged now if they have a minute.
Surprised too about lack of information, but anyways.... who cares ? Soon or late it'll be completed, I hope soon, of course. I've *not* looked at current Huw's implementation.... I lost interest in DIB engine long time ago. It's just a pity that my patchset got broken, so who needs the "old" dib engine should stay with an older wine version too.
I just tested the actual implementation, but, for my purposes, it doesn't speed up anything. Your mileage may vary, of course. AFAIK, most of apps needing it needs font drawing speedup, and there's still no trace of dib font drawing in new engine, and that one isn't a trivial task. My engine implemented it with some glitches, but at least it was usable. Also, I've got no idea if Huw is grabbing something of my code or not, but I guess not.
BTW, as a user, I would have liked something a bit more useful, or at least something which wouldn't break completely the "old almost working engine", as many people used it, but of course it's not under my control. Nor I've time to rebase the old one on current three, mostly because, as far as I can see, the interface is still changing too much and it'll be a very time consuming task.
So, cross your fingers (as usual) and hope :-)
Ciao
Max