ChangeSet ID: 24168 CVSROOT: /opt/cvs-commit Module name: lostwages Changes by: jnewman@winehq.org 2006/04/11 09:20:43
Modified files: wwn : wn20060324_309.xml wn20060402_310.xml
Log message: Francois Gouget fgouget@free.fr Spelling fixes
Patch: http://cvs.winehq.org/patch.py?id=24168
Old revision New revision Changes Path 1.2 1.3 +10 -11 lostwages/wwn/wn20060324_309.xml 1.2 1.3 +7 -7 lostwages/wwn/wn20060402_310.xml
Index: lostwages/wwn/wn20060324_309.xml diff -u -p lostwages/wwn/wn20060324_309.xml:1.2 lostwages/wwn/wn20060324_309.xml:1.3 --- lostwages/wwn/wn20060324_309.xml:1.2 11 Apr 2006 14:20:43 -0000 +++ lostwages/wwn/wn20060324_309.xml 11 Apr 2006 14:20:43 -0000 @@ -206,7 +206,7 @@ it won't for quite some time. It will b software specifically targets Vista, although it's likely Microsoft Office will lead the way. It's only been within the last year or so we've seen Windows 98 begin to be unsupported. So it'll be a while before -we have to worry Vista (especially now that the release has been pushed +we have to worry about Vista (especially now that the release has been pushed out until 2007.)</p>
<p>Mike Hearn shared some info this week about some of the API changes @@ -217,7 +217,7 @@ Potentially this is old news, but via Ra <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnlong/html/AppComp.asp"> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnlong/html/AppComp.asp</a></ul></p><p>
-Which talks about Vistas application compatibility. Interesting points +Which talks about Vista's application compatibility. Interesting points that stand out: <ul> <li> They are dropping WinHelp and CHM support. You'll have to install it @@ -232,7 +232,7 @@ that stand out: error is suppressed to stop installers tripping up).</li>
<li> They dropped D3D RM. Not many apps use this but I think at least my - fathers sailing game does.</li> + father's sailing game does.</li> </ul></p><p> So there we have it - this appears to be the first release in which they simply started dropping APIs. @@ -282,10 +282,10 @@ It's actually defined as:
<p>Not so pretty, eh? It also generates GCC warnings due to the casts, which is generally considered a bad thing. Mike McCormack sent a series of patches -last week to replace code like that. It sparked some controversy whether his +last week to replace code like that. It sparked some controversy over whether his patches were actually better or not. Rob Shearman fired the first shot:</p> <quote who="Rob Shearman"><p> -Why don't we fix the macros as suggested by Francois, rather than +Why don't we fix the macros as suggested by François, rather than preventing its use? It seems like a big waste of time to have submitted all of the patches to the files using windowsx.h when fixing the macros is necessary for Winelib anyway.</p></quote> @@ -296,15 +296,15 @@ No, it's not a waste of time. Having wa far more important than any warnings that might be in 3rd party winelib code. </p><p> -Francois' solution is still not perfect, as it requires use of a +François' solution is still not perfect, as it requires use of a non-portable C construct. </p></quote> -<p>Rob didn't think that was an issue and reminded everyone of Francois' +<p>Rob didn't think that was an issue and reminded everyone of François' original idea:</p> <quote who="Rob Shearman"><p> We're trying to work around GCC warnings that probably aren't generated using any other compiler so using non-portable C constructs is perfectly -fine. Here is Francois' solution again: +fine. Here is François' solution again: <ul><code> #ifndef WINE_CAST<br /> # if __GNUC__<br /> @@ -315,8 +315,7 @@ fine. Here is Francois' solution again: #endif<br /><br />
#define Header_SetImageList(hwnd,himl) - (HIMAGELIST)SNDMSGA((hwnd),HDM_SETIMAGELIST,0,(LPARAM)himl) - WINE_CAST(HIMAGELIST, SNDMSGA((hwnd),HDM_SETIMAGELIST,0,(LPARAM)himl)) +   WINE_CAST(HIMAGELIST, SNDMSGA((hwnd),HDM_SETIMAGELIST,0,(LPARAM)himl)) </code></ul></p><p>
It seemed to be ignored by both you and Alexandre last time it was sent, @@ -358,7 +357,7 @@ typesafe, it just looks like it is.</p>< within applications:</p> <quote who="Rauschi"><p>
-I think it would be very useful to disallow an application started with wine i +I think it would be very useful to disallow an application started with wine to connect to the network/internet by an options flag.</p></quote>
<p>That's a valid question - a lot of apps like to "phone home" and that's Index: lostwages/wwn/wn20060402_310.xml diff -u -p lostwages/wwn/wn20060402_310.xml:1.2 lostwages/wwn/wn20060402_310.xml:1.3 --- lostwages/wwn/wn20060402_310.xml:1.2 11 Apr 2006 14:20:43 -0000 +++ lostwages/wwn/wn20060402_310.xml 11 Apr 2006 14:20:43 -0000 @@ -285,7 +285,7 @@ wasn't much discussion other than a bunc <topic>Integration</topic> <p>Some rumblings began a few weeks ago about work to support Photoshop plugins in Gimp using Wine. Well, that's now a reality. Dan Kegel -forwarded a message to wine-devel wit a link to the PSPI project:</p> +forwarded a message to wine-devel with a link to the PSPI project:</p> <quote who="Dan Kegel"><p> I've been hearing rumblings about people using Wine to run windows photoshop plugins on Linux Gimp, @@ -310,7 +310,7 @@ Unlike GIMP plug-ins, 3rd-party Photosho interface library. (GIMP plug-ins use GTK+, obviously.) This is because 3rd-party Photoshop plug-ins are usually available both for the Windows and Macintosh versions of Photoshop. Typically each company uses some homegrown -widget library, with a look and feel that is widely different than the normal +widget library, with a look and feel that is widely different from the normal Windows common control look and feel, or the GTK+ look and feel. </p></quote>
<p>Ironically, we covered this topic about 2 and a half years ago in @@ -492,7 +492,7 @@ desktop mode:</p>
<p>Tony Lambregts thought of some of the problems with it:</p> <quote who="Tony Lambregts"><p> -So if I understand this correctly all programs will share the same +So if I understand this correctly, all programs will share the same desktop. Is it also true that I cannot specify in winecfg that one program can run full screen and another in a desktop window. </p><p> @@ -501,17 +501,17 @@ If this is the case we will have a fair
<p>Vitaliy Margolen cited a specific example that could be a problem:</p> <quote who="Vitaliy Margolen"><p> -Ok so now say with Steam and all of it's games - it will be almost 100% -unusable! Because we still haven't fixes managed/unmamaged windows. And +Ok so now say with Steam and all of its games - it will be almost 100% +unusable! Because we still haven't fixed managed/unmamaged windows. And Steam itself would be on top of everything. So the way people were able -to work-around this is by putting Steam into virtual desktop. Now that +to work-around this is by putting Steam into a virtual desktop. Now that means their game will run in the same desktop as well. </p><p> We really really really have to fix managed/unmanaged mode then. I can't even imagine how many people will stay with current or older Wine because of this patch. </p><p> -Also I remember some users were using other two parameters of the desktop +Also I remember some users were using the other two parameters of the desktop (top left corner - changing manually in the registry). I didn't seen anything that indicates they are still supported with this patch. </p></quote>