I'm no actual dev here by any means, but I think anything more than setting up the extreme basics would take away from the work done on 8, and 9. As not much uses 10 yet it would be a bit premature to do a ton of work on it. Porting the current code if only to the point of 10 working as well as 9 or 8 without the fancy new calls would suffice for now, and yes, I also think we should have a Vista version if only for the sake of consistency, it wouldn't really be any different than XP for us at the core just throwing the tag up there.
<br><br>I say focus SoC on 8 and 9, imagine having a more complete 8 and 9 then 10 would be cake, as I understand it all it does it add new calls right? And possibly dig up the theming zombie, so we might have that finally lol.
<br><br><div><span class="gmail_quote">On 3/10/07, <b class="gmail_sendername">Stefan D�singer</b> <<a href="mailto:stefandoesinger@gmx.at">stefandoesinger@gmx.at</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;">
Hi,<br>Thinking about SoC I though that starting a DirectX 10 implementation may be a<br>good summer of code project. I do not mean implementing the full d3d10 lib,<br>that would be way to much, more starting the infrastructure. Henri disagreed
<br>with the idea, so I thought I'll write a mail for public discussion :-) .<br>Looking at the timeline for SoC I hope it isn't too late.<br><br>My idea is to start a d3d10 implementation up to the following point:
<br><br>-> Add a winver Windows Vista to make version checkers happy :-)<br>-> Create the d3d10 lib and start the .idl file for header generation<br>-> Write stubs for the functions to allow the app to create all the interfaces
<br>-> Write test cases for reference counting. ddraw and d3d9 show that Microsoft<br>does not stick to its own COM rules<br>-> Make methods that have already 1:1 equivalents in wined3d call wined3d. Add<br>other methods as required to wined3d.
<br>-> Implement them as far as you feel like :-)<br><br>I think the good thing about this is that there are is not much knowledge<br>about wined3d and d3d10 necessary at the start. The one who works on it can<br>learn the d3d10 interface while writing the stubs and learn about wined3d
<br>when starting to call it.<br><br>Opinions? Suggestions?<br><br>Cheers,<br>Stefan<br><br><br><br><br></blockquote></div><br><br clear="all"><br>-- <br>Cheers,<br>Bryan