2018-04-11 6:07 GMT+02:00 Kieran Duggan <kieranduggan15@gmail.com>:
> Hello,
>
> So I recently received an email informing me that I have the option of
> refining or improving the list of D3DX functions that I came up with for my
> proposal.
> My current time line and list isn't a very good one to say the least.
> Basically, in the interest of time, I put together the proposal by grabbing
> a set of functions I saw in spec files marked with 'stub' without much
> thought.
>
> Clearly that wasn't optimal, so I'm pretty happy that I don't have to stick
> with that poorly put together list. It doesn't really represent my best
> work,
> and I'd like to do better, so I'm reaching out here in hopes that
> someone can point me in the right direction on how to start compiling a
> more meaningful list and time line to go with it.
>
> My idea right now is just to look at the stubs and cross reference that with
> MSDN
> to try and get a grasp of how they might be implemented and move on from
> there.
> maybe the MSDN documentation can help me find related functions that would
> make sense to work on together?

Yeah, that should be a good starting point. You're probably going to
find terms / techniques you don't know much about, so you may need to
branch out from there a bit in your research. Also looking at our
current d3dx9 implementation and tests might be helpful.
FWIW, notice that there are also a bunch of interface methods (some of
which are mentioned in our Summer of Code wiki page), rather than
plain functions, that are stubs or otherwise not complete. Just in
case you didn't see them earlier.

No pressure, take your time, but let us know when you make progress.
Feel free to ask specific questions if you have any.