ChangeSet ID: 31373 CVSROOT: /opt/cvs-commit Module name: lostwages Changes by: jnewman@winehq.org 2007/09/10 12:21:52
Modified files: wwn : wn20070312_325.xml
Log message: Francois Gouget fgouget@free.fr WWN325 spelling fixes
Patch: http://cvs.winehq.org/patch.py?id=31373
Old revision New revision Changes Path 1.1 1.2 +11 -11 lostwages/wwn/wn20070312_325.xml
Index: lostwages/wwn/wn20070312_325.xml diff -u -p lostwages/wwn/wn20070312_325.xml:1.1 lostwages/wwn/wn20070312_325.xml:1.2 --- lostwages/wwn/wn20070312_325.xml:1.1 10 Sep 2007 17:21:52 -0000 +++ lostwages/wwn/wn20070312_325.xml 10 Sep 2007 17:21:52 -0000 @@ -118,7 +118,7 @@ Linux), and a Mac version's on the way.< posts="9"
<topic></topic> -<p>Microsoft's standard routine for introducing new API's is to ship +<p>Microsoft's standard routine for introducing new APIs is to ship the new libraries with applications for a few years until they're simply shipped with the operating system. We've seen this with a lot of apps including games that install new versions of DirectX and things like @@ -235,7 +235,7 @@ later. </p><p> Next problem I still have is that pdf2png and svg2png won't link now. Not sure why's that. Also note that binaries generated by winegcc are -in fact a small script calling wine to load the actualy .exe.so file +in fact a small script calling wine to load the actual .exe.so file generated. This is not much worse than what libtool already does for us, but we may be able to get to plain binaries since we don't use any native Windows binaries and so the wine loader should not be necessary. @@ -287,7 +287,7 @@ to it. From there, all the new features Stefan Dösinger proposed someone should take this up as a summer of code project and outlined the tasks that need to be done:</p> <quote who="Stefan Dosinger"><p> -Thinking about SoC I though that starting a DirectX 10 implementation may be a +Thinking about SoC I thought that starting a DirectX 10 implementation may be a good summer of code project. I do not mean implementing the full d3d10 lib, that would be way to much, more starting the infrastructure. Henri disagreed with the idea, so I thought I'll write a mail for public discussion :-) . @@ -305,7 +305,7 @@ does not stick to its own COM rules</li> other methods as required to wined3d.</li> <li> Implement them as far as you feel like :-)</li> </ul></p><p> -I think the good thing about this is that there are is not much knowledge +I think the good thing about this is that there is not much knowledge about wined3d and d3d10 necessary at the start. The one who works on it can learn the d3d10 interface while writing the stubs and learn about wined3d when starting to call it. @@ -341,7 +341,7 @@ on OpenGL and included in the 2.0 spec. <a href="http://www.winehq.org/pipermail/wine-devel/2006-November/052375.html">pointed out</a> a few months ago that there's an HLSL to GLSL converter. </p><p> Anyway, back to the topic at hand: DX 10. Ivan wasn't sure DX10 should -count as an SoC project:</p> +count as a SoC project:</p> <quote who="Ivan Gyurdiev"><p> Yes, I am sure wine will benefit greatly from a d3d10 stub, mapping 1-to-1 to wined3d where possible, but is it really a project that @@ -366,7 +366,7 @@ The idea is that our main Direct3D engin Direct3D versions, from Direct3D 1 to Direct3D10. Admittedly, the core functionality that is equal between d3d1 and d3d10 is comparably small, and the part that exists should work pretty well by now. But work on d3d10 games -can definitly fix bugs in d3d9 apps accidentally, in the same way the d3d7 +can definitely fix bugs in d3d9 apps accidentally, in the same way the d3d7 merge fixed bugs in wined3d that affected d3d9 apps. </p><p> Also consider that d3d10 may need some architectural changes to wined3d. I @@ -377,11 +377,11 @@ that we have to turn a few core parts up Of course having one SoC project on d3d10 does not exclude someone else who wants to do something do a SoC project on d3d9 :-) . Ideas would be Overlay support for movie players or the d3dx9_xy helper DLLs (although those are -maybe out of scope for wine). Or even a completely different area of DirectX. +maybe out of the scope of wine). Or even a completely different area of DirectX. DirectSound, DirectPlay, ... </p><p> One problem is nowadays that wined3d is pretty advanced already, and the -learning curve is rather hard already. D3D10 is in my eyes an oportunity of +learning curve is rather hard already. D3D10 is in my eyes an opportunity of an exciting project which allows a new developer to grow into wined3d. I personally won't start hacking on d3d10 immediately, I'll continue to work on d3d9 and below apps. The state of d3d9 does not justify that yet. @@ -417,7 +417,7 @@ work for the start. It is a long way to Regaring Vista, the nice thing is that Students get Educational licenses cheap. But the license should be checked carefully. I for example may use it only for educational purposes. As I am working for CodeWeavers my hacking on -wine isn't purely for educational purposes. No idea of SoC can be considered +wine isn't purely for educational purposes. No idea if SoC can be considered an educational thing. </p></quote>
@@ -500,7 +500,7 @@ use snail mail/fax from their web site). <quote who="Shachar Shemesh"><p> Wouldn't a paper saying they keep their rights, but approve the LGPL distribution also work? Would that still require us to have a written - statement? After all, we do not require written from other people. + statement? After all, we do not require written statements from other people. </p></quote>
<p>James Vasile replied with:</p> @@ -580,7 +580,7 @@ appear to be due to missing redistributa Oh, or commonly-needed registry entries. </p></quote>
-<p>So wait.. this makes things easier, why is it bad you ask? Well, +<p>So wait... this makes things easier, why is it bad you ask? Well, installing native components has led to lots of problems in the past. (It's also led to millions of successful program installations.) Any time native components get installed they simply provide less of a