On Tue, Feb 23, 2010 at 5:29 AM, Francois Gouget <fgou...@free.fr> wrote: >> http://wiki.winehq.org/SummerOfCode#head-5cdc861e4369f94f0af19d09710d33d76b1f5c64 >> Current text: >> ... >> Let's try making the smallest possible demo games that show problems >> in Wine, and file bugs for what we find (along with the source for the >> games/demos)." > > This does not seem related to Wine to me, except in a very round-about > way. IMHO a better way would be to improve the conformance tests as > running them is already automated and they are even clearer about what > is being tested.
OK, next draft: http://wiki.winehq.org/SummerOfCode#head-8d0895f237c9c3579ffe4282412bbbf2c8cd019b Current text: "Direct3D - Conformance / Performance / Interactive tests Possible Mentors: DanKegel Even small demos show interesting problems in Wine (see e.g. http://bugs.winehq.org/buglist.cgi?quicksearch=3drad, http://bugs.winehq.org/show_bug.cgi?id=21817 ) There are lots of tools (see http://wiki.winehq.org/GameEngines ) that make developing tiny games easy; they often come with tutorials or examples that might let you isolate problems We would like to capture the problems these expose by writing conformace tests (possibly WINETEST_INTERACTIVE ones, if they can't be automated) or performance test tools (as part of programs/dxtest, perhaps), or at the very least bug reports It'd be nice to also fix some of the problems, too." Is that closer?
