2009/5/24 Massimo Del Fedele <span dir="ltr"><<a href="mailto:max@veneto.com">max@veneto.com</a>></span><br><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'm looking forward to this hitting upstream :) Have the architectural<br>
issues been solved yet?<br>
<br>
</blockquote></div>
Nope, and I think they will not be solved soon. Not by me, anyways.<br>
I made my engine because I was needing it, but Alexandre don't like<br>
its architecture, so it won't be merged even if, IMHO of course, it<br>
could be done as an "alternative experimental driver" in parallel to<br>
current winex11 one, which could spread its usage and testing a lot<br>
more. But Alexandre didn't like that solution, ever.<br>
</blockquote><div><br>I assume all this took place on IRC because unless I missed it,<br>Alexandre hasn't deigned to comment on here about what the <br>right architectural solution would be. <br><br>Sorry to sound like a stuck record but the Wine website still lists<br>
"write a DIB engine" as a requirement, and every time someone<br>does, the patches dissapear down a hole because they're "not<br>right". Someone document what "would be right", or take "write<br>
a DIB engine" off the list. I'd love to have a go at documenting it<br>myself, but I don't have the time to reverse engineer it from a<br>few years' worth of rejected solutions.<br><br>--<br>Chris<br></div>
</div>