I kind of agree with him too, Since we can't really just test every single API, obviously, the best thing to do is setup a 1.0 test quite of sorts, where you have either a ton of little applications trying things whether theyre known to work or not, or one big wine made ap which tests as much as we can, which gives nice detailed output or something, and reaching 100% compatibility with this "Toolbox" of sorts would let them drop the
1.0 down. Or we could say in a few years have some kind of huge community event, where everyone goes through alllllll the possible appdb aps they can and give updated test results, when say 75%+ hit platinum you could call it a mile stone.
<br><br><div><span class="gmail_quote">On 3/20/07, <b class="gmail_sendername">Robert Shearman</b> <<a href="mailto:rob@codeweavers.com">rob@codeweavers.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dave Bialac wrote:<br>> My personal thought is that Wine should head in the direction of 100%<br>> compatibility with a particular version of Windows. Anything that ran<br>> on that version should run on Wine 1.0
with no problems. Any thoughts?<br><br>That just isn't going to happen any time soon. If we were 100%<br>compatible with one version of Windows then we would be 99% compatible<br>with other versions too. That would be really nice, but due to the way
<br>we implement Wine using black-box testing there are always going to be<br>implementation differences and there are known bugs in many areas that<br>we simply don't have the developer resources to fix at the moment.
<br><br>I think the only viable way to drive for 1.0 is feature or applications<br>targets, with applications compatibility driving test cases and bug fixing.<br><br>--<br>Rob Shearman<br><br><br><br></blockquote></div><br>
<br clear="all"><br>-- <br>Cheers,<br>Bryan