[GSoC] My (new) proposal for GSoC 2013

[Gediminas Jakutis]

On Fri, Apr 5, 2013 at 10:08 AM, Stefan Dösinger
<stefandoesinger at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am 2013-04-04 22:52, schrieb Gediminas Jakutis:
> 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.

Good day!

This was discussed on the IRC a bit. The idea is to write
[performance?] tests that are to be used for dxdiag. (I suppose that
includes that funny spinning dx logo cube test found on the native
dxdiag).
Regarding the way of testing if opengl works - I was thinking in the lines of:
Making a GUI tool that would let simple users test if d3d and opengl
works along with providing info on current wine-specific d3d / opengl
settings / specs and similar thing. i.e. a user-friendly tool for,
uhm, simple users. Something related to what wine crash dialog is: I
bet many "simple" users were not much aware of Wine's debug output and
bug reporting. Meanwhile the crash dialog was something like - "Hey!
Something crashed! Take this info and report it if it's a bug!".
So yes, the idea idea of the "if works" test is to make a
user-friendly GUI tool. I believe that would be a great help in cases
for some reason opengl [and along d3d] breaks for a user, so it could
be easily identified early, thus helping to avoid situations where the
user looks into other possible causes / asks around for quite some
time before realizing opengl w/ d3d broke. Also, that might help avoid
possible invalid bug reports that would caused by a broken opengl /
d3d, yet reported without the user checking that properly.

> 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.

I suppose when making those dxdiag-orientated tests, working with
built-in dxdiag a bit might just come naturally.

I hope that makes my intentions for GSoC a bit more clear. And, sorry
- I should've gone with more detail on previous letter, indeed.

--
Gediminas Jakutis
LDK Varčiai www.varciai.lt