-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 2013-04-04 22:52, schrieb Gediminas Jakutis:
Hello!
My previous application[1] turned out to be a total failure, hence making a completely different one. My proposal this time goes as follows: Write various D3D tests, mostly focusing on ones that can be later re-used for dxdiag in one way or another. Along with writing a tool that would allow users to easily test if d3d and wgl / opengl work & are set up properly.
There is some merit to the proposal, but it needs a lot more detail. We already have a lot of d3d tests (see dlls/{ddraw,d3d8,d3d9,d3d10core,dxgi}/tests/) . Those already provide a way to test if opengl works ok, to some extent - those tests are fairly strict and only pass on nvidia and r600g.
Extending dxdiag (and adding the information dialog) might be a good idea. I think there have been some projects concerning that in the past, I recommend to do some research.
Lastly there are some bug reports which need tests, e.g. 10164 and 29052. Bug 29052 should provide a nice introduction into ddraw/d3d programming in Wine, but those two bugs do not provide enough work for a full gsoc project. Some additions will be needed. However, Alexandre has stated that writing tests for the tests sake (i.e., no application that uses the testsed behavior) is not a good idea. Picking any number of apps which have bugs that are not understood yet and attempting to fix them is a bad idea as well because you don't know how long it'll take you to fix them until you have some idea what the actual problem is.