March 2009 - Wine-devel - list.winehq.org

flattering words about winetricks
by Dan Kegel 24 Mar '09

24 Mar '09

http://www.vivaolinux.com.br/dica/Winetricks-turbinando-seu-wine-sem-dores-… says "created by Dan Kegel, who was in a state of grace when he had this brilliant idea..." :-) (In case anyone has forgotten, winetricks is about the sixth in a long series of front-ends that try to make it easier to install software in wine, so it was hardly my idea. But I appreciate the sentiment.) - Dan

4 3

Re: Anything wrong with these patches ?
by Ricardo Filipe 23 Mar '09

23 Mar '09

2009/3/23 Massimo Del Fedele <max(a)veneto.com> > winex11.drv: SetDIBits fails when startscan != 0 > http://www.winehq.org/pipermail/wine-patches/2009-March/070788.html > (solves a bug on SetDIBits when transfer partial bitmap) > > gdi32/path.c -- Allow PATH_ExtTextOut() handle non printable characters > http://www.winehq.org/pipermail/wine-patches/2009-March/070768.html > (solves broken text output when text contains non-printable chars, as > space) > > gdi32/path.c - Fix PATH_ExtTextOut() for MapModes != MM_TEXT > http://www.winehq.org/pipermail/wine-patches/2009-March/070770.html > (solves bad placement/scaling on text when MapModes != MM_TEXT, AutoCAD bug > 17170) > > Ciao > > Max > > > > maybe wait until tomorrow to see if they get in or not. julliard came today from holidays and hasn't see every patch. ;)

1 0

Re: comctl32: implement TCM_REMOVEIMAGE (try2)
by Vitaliy Margolen 23 Mar '09

23 Mar '09

Nikolay Sivov wrote: > Changelog: > - try2: fix for several items with a same image case > - implement TCM_REMOVEIMAGE What about this comment from msdn? --------- The tab control updates each tab's image index, so each tab remains associated with the same image as before. If a tab is using the image being removed, the tab will be set to have no image. --------- It implies that indexes should be adjusted if you remove an image somewhere at the front or middle of the image list. Don't see you doing this in your patch. Vitaliy.

2 2

Re: setupapi: Don't copy into a NULL PathBuffer, and remove an invalid check for size < MAX_PATH (Coverity 888).
by Ricardo Filipe 23 Mar '09

23 Mar '09

my next task was to fix this eheh. i think it would make more sense to just change if(!params->PathBuffer && !params->PathBufferSize) to if(!params->PathBuffer) as it was talked about in irc, it doesn't make much sense to check for pathbuffersize when pathbuffer is null... the max_path removal was a mistake from following msdn documentation :\ 2009/3/22 James Hawkins <truiken(a)gmail.com> > --- > dlls/setupapi/dialog.c | 12 +++++++----- > 1 files changed, 7 insertions(+), 5 deletions(-) > > > >

2 4

Re: comctl32: Implement TCM_REMOVEIMAGE message
by Nikolay Sivov 23 Mar '09

23 Mar '09

> >/From c419ca8f87ae3103e63604d9646d3851a5d959e7 Mon Sep 17 00:00:00 2001 > /From: Nikolay Sivov <bunglehead at gmail.com <http://www.winehq.org/mailman/listinfo/wine-patches>> > Date: Sun, 22 Mar 2009 18:43:46 -0400 > Subject: Implement TCM_REMOVEIMAGE It's wrong in case when several tabs use same image. Please ignore it.

1 0

Re: wined3d: Document the correlation of gl_shaders and num_gl_shaders with an assertion (Coverity 905).
by Henri Verbeet 22 Mar '09

22 Mar '09

2009/3/22 James Hawkins <truiken(a)gmail.com>: > --- > dlls/wined3d/vertexshader.c | 3 +++ > 1 files changed, 3 insertions(+), 0 deletions(-) > I guess the nicer way to make Coverity shut up would be to replace "if(shader->gl_shaders) {" with "if (shader->num_gl_shaders)". Wouldn't the code in find_gl_pshader() in pixelshader.c cause the same warning though?

2 1

Chromium unit test suite as source of Wine tests
by Dan Kegel 22 Mar '09

22 Mar '09

Hey folks, the chromium project has a very nice unit test suite, and the chromium team pores over it with purify and now, on linux, valgrind to make sure everything is clean. This makes it a rather attractive test case for Wine even if Wine isn't really trying to run Chrome itself. I just filed three bugs for the problems found by chromium's base_unittests.exe, net_unittests.exe, and test_shell_tests.exe ( http://bugs.winehq.org/show_bug.cgi?id=17813 http://bugs.winehq.org/show_bug.cgi?id=17820 http://bugs.winehq.org/show_bug.cgi?id=17810 ), on top of the old bug about running chromium's ui_tests.exe http://bugs.winehq.org/show_bug.cgi?id=16552 I also added a suggestion about this in http://wiki.winehq.org/SummerOfCode It would be cool to see this test suite run daily to look for wine regressions somehow. OK, back to the native linux port of chromium... Cheers, Dan

1 0

Re: GSoC 2009 Proposal - AppDB Assistant
by André Hentschel 22 Mar '09

22 Mar '09

Ben Klein schrieb: > Grabbing the version number of the application from the EXE metadata > could prove to be unreliable. A lot of Windows apps don't include > metadata, or include unusual values in the metadata. Then again, a lot > of apps don't make it easy to see what the version you're using is in > any other way, and as a result there are a lot of "1.0" versions on > AppDB that map to "initial retail version". > > One example is Theme Hospital, which as the original retail version > was released as "Beta 4", and Bullfrog provided a patch that upgraded > to "Beta 5". The only hint of version numbers is provided by the patch > itself, and as a result some user wanted to submit a "1.0" version to > indicate the original retail release. As I was a supermaintainer of > Theme Hospital and already had the "Beta 4" version, I removed the 1.0 > version and engaged in a lengthy email discussion over whether the > retail release was "Beta 4" or "1.0". > > I am also afraid of reading this data, but we could give the user the choice to review it and correct it. > > There has been discussion about "preconfiguring" Wine with AppDB data, > and the general consensus is that it's a bad idea. We run the risk of > becoming like wine-doors, playonlinux, and other tools we don't > support at WineHQ. The biggest problem is that there is no way to > determine if any particular configuration will still work when a new > version of Wine or a new version of the app is installed. There are > also cases where installing a workaround/native DLL for one app will > cause a whole lot of others to break. > > It is a hard discussion, so lets have it when we got the AppDB Assistant running ;) No, really, the basic idea is great, but we don't should do all at once. For GSoC i think the best parts are the basic software implementation and the communication to the server.

1 0

GSoC 2009 Proposal - AppDB Assistant
by Illya Klymov 22 Mar '09

22 Mar '09

Hi all! A new GSoC is coming, and i have an idea which can may (or may not) serve as a proposal for a Wine project. Let's speak about it not as an application (so I wouldn't tell a lot about myself) but as an idea for application. AppDB is an excellent service for helping users dealing with one or another software. Unfortunately, currently i see several problems, which decrease it's efficiency: 1) there are tons of successful (or maybe not successful) reports, which were not submitted to AppDB. People are too lazy to fill many forms. A lot of users will just go away instead of filling report about application. 2) often in order to run an application you should follow some weird instructions, which sometimes miss some important steps, or require additional research by yourself. So, let's imagine we have a software which I call "AppDB Assistant" with following functionality: 1) an ability to quickly submit a report about application to AppDB. A lot of data (Wine version, Linux distribution, wine settings) could be obtained automatically. An application information with high probability could be fetched from meta data, stored in EXE file. In general, i see that like after closing an app I see additional screen "Please take a couple of seconds and send feedback about your experience with $SOFTWARE_NAME to AppDB", and buttons "Platinum","Gold", etc. Of course this should be configured via winecfg (if user do not want to obtain such data) 2) an ability to generate a "configuration guide" - in this mode an "expert user" selects important data to be included into a guide (for example that app runs _only_ under Windows XP emulation, an important registry values etc.). As a result a special file, describing an app-specific configuration of wine is uploaded to appdb 3) an ability to "preconfigure Wine". That means that based on "configuration guide" created on step 2 "AppDB Assistant" can configure wine in one click. If any additional dlls are required a warning message is displayed with possible information where to obtain them. I see the following benefits on such software: 1) increasing appdb actuality - with a way more data from users we can provide more accurate info; 2) simplified regression testing - for example if user downloaded a "configuration guide" and it didn't work with newer wine - this is a possible regression (decreased chance of human error) I realize that this is quite a big project, involving a different parts of Wine, but I'll be glad to hear response from community about this idea and which part probably could fit best for GSoC. Feel free to ask any question if something is unclear. P.S. Sorry for my bad English, it is far away from being my mother tongue. Best regards, Illya Klymov

2 1

Re: wine web pages update
by Vít Hrachový 21 Mar '09

21 Mar '09

Apostolos Syropoulos wrote: > > > Hello, > > I believe you the person responsible for the Wine web pages. If this is not true, > please disregard the rest of this message and accept my apologies for this > uninvited intrusion. > > Previous versions of the wine web pages includes information about Solaris/OpenSolaris > binaries and info about these systems. Now there is no mention about Solaris/OpenSolaris! > For example, the first page says "Run Windows Applications on Linux, BSD and MacOS". > OK Solaris is a commercial product but so is MacOS! Since I do release binary packages > of wine for both Solaris and OpenSolaris at http://ww.sunfreepacks.com could you include > this info in the download section. Also, could you please say something like "Run Windows > Application on most Unix and Unix-like systems". This shows impartiality and is far more > friendly. > > Thanks in advance for your cooperation. > > Apostolos Syropoulos Hi Apostolos, I can see no Wine packages on the link mentioned above. Maintainers of Wine webpages could be reached on wine-devel(a)winehq.org. Including wine-devel on list. BTW. There are IPS packages of 1.0.1 for OpenSolaris available (1). Recent Wine compiles well under OpenSolaris too (1.1.17). Cheers Hark 1) 2) http://pkg.opensolaris.org/contrib/en/index.shtml

4 3