May 2009 - Wine-Devel - list.winehq.org

RE: Severity levels

by Nicklas Börjesson

> You'd be surprised... We'll I've looked around at "invalids", but to me it seems that people in general(with a few exceptions of course), tries quite hard until they file a bug report. At least way harder than they do in other FOSS projects I have been involved in, so I can't really say that I would think you've got a problem. At least not yet. Despite the support forum only have one list. More stuff on the wiki would help too. >Not all critical bugs are caused by the loader. It's possible for >d3d/ole/etc. to have a similar effect. Yes, it is possible, but not likely enough to warrant an extra severity level. Yes, I have looked. >Keep in mind, most developers are unpaid as well. They're the ones >fixing the bugs, not users. While users are important, no work gets >done without the developers. I know that most developers are also unpaid. With "maintained" I didn't only mean maintainers of versions and so forth. >Developers have no way to prioritize one >user over another. The best way to prioritize *your* bug is to make a >*good* bug report. Make sure all needed information is included. Get a >testcase if possible. Provide the needed traces, etc. Even better, is >to write a patch yourself. The source is there, and there is nothing >stopping you from writing a patch. Again. This is not what I am talking about. I am not relevant because I am also an experienced developer, so I have no problems with these things. I can patch like there is no tomorrow, given time. What I am talking about the fact that the ordinary users priorities are very important. Currently they are either: 1.Completely disregarded or 2. If they follow the instruction(where "commons sense" is not mentioned), they're forced to adhere to severity levels that distort or hide their opinion of the problem. And for each user reporting there are dozens that are not. Bad will. It just feels like the entire project should become a bit more user-centric. Now I am not just talking about shinier graphics but about attitude. Maybe soften up a bit ask oneself, "WHY did this person ask this stupid question?", "WHY did he do this EVEN though it says do this?" or "How would I feel if someone said this to me?". //Nicklas

May 3, 2009

Re: RFC on Base Wine Config

by Ben Klein

2009/5/3 Paul TBBle Hampson <Paul.Hampson(a)pobox.com>: > On Sun, May 03, 2009 at 03:07:35PM +1000, Ben Klein wrote: >> It's NOT a networked drive, is it? Drive mappings are the only way to >> tell Wine and apps running in Wine where your files are in your >> host-system (Unix-style) filesystem. > > The discussion on wine-devel in April related to bug 15883 suggested the > implementation of \\?\unix\ which would in turn allow programs access to > things that aren't mapped in the DosDevices list, unless specifically > disallowed (which wasn't discussed at the time) > > A quick look at [1] suggests that \\?\unix\etc/hostname would seem to be > a reasonable thing to expect to work under Wine. But that requires either 1) the app to be aware of \\?\unix, or 2) Wine to map \\?\unix/foo/bar when no drive mapping to /foo/bar exists. #2 would also require some way to be configured to allow the equivalent of removing the default Z: drive mapping for people who want it. However, it would not provide any additional functionality and could easily be considered a waste of time. Of course, that's not up to me ;) >> Note that it would be a breach of security to allow some method to >> access / without a direct mapping in dosdevices. > > How so? I'm fairly sure this suggestion was dismissed in the > above-mentioned email discussions as well. AFAIK, the main reason people remove the Z: mapping is a security concern. It's not an issue for me, but some people like to restrict the files that win32 apps can access to a subdirectory in $HOME. If there's some workaround to access files outside the drive mapping (assuming pure win32 of course :D ), then unless it can be disabled by the user, it's a security breach.

May 3, 2009

Re: Romanian translation (again)

by Dimitriu Petru

2009/5/3 André Hentschel <nerv(a)dawncrow.de>: > Dimitriu Petru schrieb: >> >> I'm here again for the Romanian translation of Wine. >> I only want somebody to change in the translation "Proprietă?i pentru" >> with "Proprietăţi pentru" because it shows ugly in ReactOS. >> >> Thanks in advance, >> Petru >> >> >> > > Patch sent: > http://www.winehq.org/pipermail/wine-patches/2009-May/072559.html > Thank you, André Hentschel.

May 3, 2009

Re: Romanian translation (again)

by Ricardo Filipe

2009/5/3 Dimitriu Petru <petrimetri(a)gmail.com> > I'm here again for the Romanian translation of Wine. > I only want somebody to change in the translation "Proprietă?i pentru" > with "Proprietăţi pentru" because it shows ugly in ReactOS. > > Thanks in advance, > Petru > > > you can send translations patches to wine (you don't need to be worried to work for reactOS for this kind of patches, if that's your problem), no need to ask other people to make the patches :P

May 3, 2009

Re: [shell32] stub for ExtractVersionResource16W

by Dmitry Timoshkov

"Stefan Leichter" <Stefan.Leichter(a)camline.com> wrote: >> Also you might be interested that according to >> http://www.geoffchappell.com/viewer.htm?doc=studies/windows/shell/shell32/h >>istory/names351.htm ExtractVersionResource16W is discontinued starting from >> Windows Vista. > > What does the second point means for wine? That means that if Microsoft has dropped that API from Vista, all apps that use it no more will function on Vista and newer Windows generation. Therefore Wine is free to drop it as well. -- Dmitry.

May 3, 2009

Re: Severity levels

by IneedAname

On Sat, 2 May 2009 16:52:06 +0200 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se> wrote: > 3. Major "Major loss of functionality for a wide range of applications > > - Isn't this just all bugs that has more than $arbitrary_number of applications linked to them? An aggregate, rather than a level? In that case #16281 would be major not minor, That is if all the applications that has that bug link to it. I think you can not find out how many applications link a bug. As that has not be coded. To find out that information you would have to scan the application data base or change the way the data base holds this data. I think you want to read bug #16284.

May 3, 2009

Re: Romanian translation (again)

by André Hentschel

Dimitriu Petru schrieb: > I'm here again for the Romanian translation of Wine. > I only want somebody to change in the translation "Proprietă?i pentru" > with "Proprietăţi pentru" because it shows ugly in ReactOS. > > Thanks in advance, > Petru > > > Patch sent: http://www.winehq.org/pipermail/wine-patches/2009-May/072559.html

May 3, 2009

Re: RFC on Base Wine Config

by Paul TBBle Hampson

On Sun, May 03, 2009 at 03:07:35PM +1000, Ben Klein wrote: > It's NOT a networked drive, is it? Drive mappings are the only way to > tell Wine and apps running in Wine where your files are in your > host-system (Unix-style) filesystem. The discussion on wine-devel in April related to bug 15883 suggested the implementation of \\?\unix\ which would in turn allow programs access to things that aren't mapped in the DosDevices list, unless specifically disallowed (which wasn't discussed at the time) A quick look at [1] suggests that \\?\unix\etc/hostname would seem to be a reasonable thing to expect to work under Wine. > Note that it would be a breach of security to allow some method to > access / without a direct mapping in dosdevices. How so? I'm fairly sure this suggestion was dismissed in the above-mentioned email discussions as well. [1] http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx -- ----------------------------------------------------------- Paul "TBBle" Hampson, B.Sc, LPI, MCSE Very-later-year Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) Paul.Hampson(a)Pobox.com Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Marcus Brigstocke http://www.marcusbrigstocke.com/pacman.asp License: http://creativecommons.org/licenses/by/2.5/au/ -----------------------------------------------------------

May 3, 2009

Romanian translation (again)

by Dimitriu Petru

I'm here again for the Romanian translation of Wine. I only want somebody to change in the translation "Proprietă?i pentru" with "Proprietăţi pentru" because it shows ugly in ReactOS. Thanks in advance, Petru

May 3, 2009

Re: Severity levels

by Austin English

2009/5/2 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se>: >>> 2. Critical "Critical problem that prevents all applications from working" >>> >>> - Possible, if everyone stopped testing code completely, and also unlikely to be reported by a user. > >>No, critical bugs are usually opened by non-Linux users. > > Here I did search, and actually, most bugs have "linux" as an operating system so I couldn't come to that conclusion. > Anyway, I get your point. Still don't really see why this is a separate severity level, though. > Wouldn't this be a "wineloader" component or something? Not all critical bugs are caused by the loader. It's possible for d3d/ole/etc. to have a similar effect. >>> 3. Major "Major loss of functionality for a wide range of applications >>> >>> - Isn't this just all bugs that has more than $arbitrary_number of applications linked to them? An aggregate, >>> rather than a level? > >>No, it's actually what it say, a WIDE RANGE of applications. > > Ok..I just thought that "wide range" could be translated into a number or percentage instead of an expression. > I thought the opposite way...but couldn't possibly all bugs in wine affect a wide range of appliacations? Sure, it's just not as common as you'd think. >> Bugzilla is to track bugs, it's not a user support forum, and the bugs >> should be classified as the dev's want them to be classified. > > No, I know it is not a support forum(Is users using is as such a big problem?). You'd be surprised... > But it is nevertheless an interface towards the users of wine. A place they go to when all else has failed(hopefully). > And as such it is utterly confusing(for them) and already leads to pointless misunderstandings and frustrations > regarding, for example, the severity flag. > > Anyway. I can't help but feel that we are on completely different pages in many ways. > I think that the users should have quite a say with regards to how important a bug is, because for every user > putting in the (considerable for a user) effort of reporting a bug, there are dozens that don't say anything at all. > In wine's case, because of it's size, this might actually be hundreds. It's badwill. > > So currently, there is no way at all for users to influence these priorities. To me, user priorities would be a > considerable factor, obviously not the only one, but considerable. > I know that wine, to a large extent, Is maintained by unpaid individuals(like myself) that want to prioritize themselves. > I don't want to take that right away from them, I just feel that it's bad practice to disregard the users' priorities. Keep in mind, most developers are unpaid as well. They're the ones fixing the bugs, not users. While users are important, no work gets done without the developers. Developers have no way to prioritize one user over another. The best way to prioritize *your* bug is to make a *good* bug report. Make sure all needed information is included. Get a testcase if possible. Provide the needed traces, etc. Even better, is to write a patch yourself. The source is there, and there is nothing stopping you from writing a patch. As a developer that spends more time testing than coding/etc., I see both sides of the coin. But keep in mind, that there are thousands of users, and just as many applications. Prioritizing one user/application over the other is almost always impossible, for obvious reasons. Picking your bug instead of Bob's bug just pisses Bob off, and vice versa. So how is most bug fixing done? Developers big bugs that interest them, that affect them personally, or that have good bug reports, which makes it fixing it much easier on them. -- -Austin

May 3, 2009

RE: Severity levels

by Nicklas Börjesson

Ok..you seem to have misunderstood the tone in my mail. >Without common sense, all bug reports would be "Enhancement" requests, >or "Critical", depending on how arrogant the reporter is. Common sense >must *always* be applied. I should be needed to be applied only to the least possible amount. One should never have to think for no reason. The more "common sense" that have to be applied to make something work, the less something works by itself. Of course, you can't completely do away with common sense. I said "without common sense" to point out the problems. And, well, some have less common sense. Or a different kind. Or are just tired, stressed out or something else. So, the less common sense needed, the better, IMO. My other point is that reporters are like to become less technical. > Oh, and use "Reply to all" so you stop just hitting Austin with responses! Huh? The mailing list is cc:d, Isn't that enough? I mean, it looks on you mail you mailed me and cc:d? Doesn't the mailing list propagate messages if it is only cc:d? Have I misunderstood something? In that case I am sorry. >Rosanne is an AppDB admin. What contribution have you made to Wine? >Out of you and her, I don't think her credibility can be called in to >question. And before you ask, I'm also an AppDB admin, I package the >Debian packages for WineHQ, and have had a patch committed to Wine. >I'll even send you the git revision code if you can't find it! :D >Note that like Rosanne, even when I was a newbie submitting bug >reports, I understood the severity levels because I read the >descriptions. The descriptions are fine as is, with the possible >exception of "Blocker" (people submit "Blocker" bugs for "Normal" >issues because it blocks the thing that they're doing). It's seems you missed the ":-)". I put in the end of the sentence on credibility. It was a joke and she seems to have took it that way, since she joked back. With regards to the severity levels, to me, none of them means what one would think they do intuitively. //Nicklas PS. I am sorry if I have broken the rules of this list, but I thought I followed them. I hope you don't let this detract from my arguments. DS.

May 3, 2009

Re: RFC on Base Wine Config

by Kai Blin

On Sunday 03 May 2009 07:07:35 Ben Klein wrote: > 2009/5/3 chris ahrendt <celticht32(a)yahoo.com>: Replying to Ben's email as I didn't get Chris' email Ben replied to. I would also like to note that I don't appreciate the tone both of these emails are taking in the end. Please try to be civil. That being said, let me get to the technical part. > > I guess I am not being completely clear somewhat.... > > If I am in windows and go into explorer... > > We've been through this before. Wine is not Windows. In Wine, the > drive has to be mapped in dosdevices. > > go to a network drive. I do > > not nescisarily have to map that drive in order to run an application > > (so long as the DLLS it needs, if any, are not just on that drive). I > > can click the application > > and it runs. I realise this may be a fundamental difference between unix > > and windows but still they should theoretically run the same. The important part here is that your local drives are local drives. Don't confuse the Wine drive mappings with network drive mappings in Windows. Think about a Wine drive mapping like plugging a new hdd into your box. > > But you're NOT running the test from a network drive, are you? And > even if you were, you'd need some way to inform Wine that it's there, > which would be to map it to a drive. Does Wine even support > Windows-style shares? Nope. We could, but then you'd have to create a Samba share to allow us to use the directory. I'm pretty sure a wine drive mapping is easier and faster. > > Also from > > a command line I can do (I think if I am remembering correctly (been > > doing to much z work lately) ) //server/directory/app.exe and it will > > retrieve and run the app... (I think) That's a bit besides the point, as this is still a valid UNC path. Now imagine I've got a USB hdd with my app on it, and that's usually connected at U:, with my app being at U:\test\app.exe. Now the logic in Windows mapping my USB drive to U: is just what the wine dosdevice mapping is like. If I now tell windows to remove the USB device, my desktop link to U:\test\app.exe is not going to work anymore. > This message appears in your bug report: > > Warning: could not find DOS drive for current working directory > > '/home/cahrendt/wine-git/dlls/inetmib1/tests', starting in the Windows > > directory. Here my analogy would be a bit stretched, as in that you'd still manage to be on the USB drive while it's already been disconnected. But basically you're trying to run a program that's on a drive not connected to your wine "box". Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton.

May 3, 2009

Re: RFC on Base Wine Config

by Ben Klein

2009/5/3 chris ahrendt <celticht32(a)yahoo.com>: > > Juan Lang wrote: >>> ok then I am very confused then... >>> I deleted the / mapping all together and then ran the dotest script and >>> the make test scripts >>> dotest fails if the / mapping is not there along with the inetmib1 >>> test. I opened a bug >>> concerning the inetmib test failing and was told that my configuration >>> with the / mapping deleted >>> was an invalid wine configuration that the / is absolutely needed by wine. >>> >>> So I am confused... is it required or not? >>> >> >> It is not required. What _is_ required is that the path to the >> current executable is mapped, somewhere. I suggested you remap Z: to >> / as it's the default, and it was the most concise way to ensure that >> your configuration met the requirement. As Ben said, you could map >> any drive. Heck, you could have mapped Q: to the dlls/inetmib1/tests >> directory and the inetmib1 test would have worked, while having no >> mapping would not work. >> --Juan >> >> >> > I realise this juan... > I guess I am not being completely clear somewhat.... > If I am in windows and go into explorer... We've been through this before. Wine is not Windows. In Wine, the drive has to be mapped in dosdevices. > go to a network drive. I do > not nescisarily have to map that drive in order to run an application > (so long as the DLLS it needs, if any, are not just on that drive). I > can click the application > and it runs. I realise this may be a fundamental difference between unix > and windows but still they should theoretically run the same. But you're NOT running the test from a network drive, are you? And even if you were, you'd need some way to inform Wine that it's there, which would be to map it to a drive. Does Wine even support Windows-style shares? > Also from > a command line I can do (I think if I am remembering correctly (been > doing to much z work lately) ) //server/directory/app.exe and it will > retrieve and run the app... (I think) You should probably verify this. 2009/5/3 chris ahrendt <celticht32(a)yahoo.com>: > And you are looking at the wrong bug... 1 > The bug in question is actually : 18283 (now closed as the issue was > resolved by the mapping) not 17996. 18283 didn't come up in my search. It would have been much easier if you mentioned the bug number when you first mentioned that you reported a bug for this. > The only way to fix it was mapping the / drive or mapping the ~/wine-git directory to a physical drive for wine to use... Yes. This is how it works. This is how it always has worked. > In Windows you don't nescissarily need to map a drive to run an application from that networked drive. It's NOT a networked drive, is it? Drive mappings are the only way to tell Wine and apps running in Wine where your files are in your host-system (Unix-style) filesystem. Note that it would be a breach of security to allow some method to access / without a direct mapping in dosdevices. > Also no its not a PEBKAC it is a valid question and a request for comment not a request for insult and slam. This message appears in your bug report: > Warning: could not find DOS drive for current working directory > '/home/cahrendt/wine-git/dlls/inetmib1/tests', starting in the Windows > directory. PEBKAC QED. > Grow up.. How about you *THINK* about what you're doing and how it works before reporting obviously invalid bugs?

May 3, 2009

Re: RFC on Base Wine Config

by chris ahrendt

Juan Lang wrote: >> ok then I am very confused then... >> I deleted the / mapping all together and then ran the dotest script and >> the make test scripts >> dotest fails if the / mapping is not there along with the inetmib1 >> test. I opened a bug >> concerning the inetmib test failing and was told that my configuration >> with the / mapping deleted >> was an invalid wine configuration that the / is absolutely needed by wine. >> >> So I am confused... is it required or not? >> > > It is not required. What _is_ required is that the path to the > current executable is mapped, somewhere. I suggested you remap Z: to > / as it's the default, and it was the most concise way to ensure that > your configuration met the requirement. As Ben said, you could map > any drive. Heck, you could have mapped Q: to the dlls/inetmib1/tests > directory and the inetmib1 test would have worked, while having no > mapping would not work. > --Juan > > > I realise this juan... I guess I am not being completely clear somewhat.... If I am in windows and go into explorer... go to a network drive. I do not nescisarily have to map that drive in order to run an application (so long as the DLLS it needs, if any, are not just on that drive). I can click the application and it runs. I realise this may be a fundamental difference between unix and windows but still they should theoretically run the same. Also from a command line I can do (I think if I am remembering correctly (been doing to much z work lately) ) //server/directory/app.exe and it will retrieve and run the app... (I think) Chris

May 3, 2009

Re: RFC on Base Wine Config

by Juan Lang

> ok then I am very confused then... > I deleted the / mapping all together and then ran the dotest script and > the make test scripts > dotest fails if the / mapping is not there along with the inetmib1 > test. I opened a bug > concerning the inetmib test failing and was told that my configuration > with the / mapping deleted > was an invalid wine configuration that the / is absolutely needed by wine. > > So I am confused... is it required or not? It is not required. What _is_ required is that the path to the current executable is mapped, somewhere. I suggested you remap Z: to / as it's the default, and it was the most concise way to ensure that your configuration met the requirement. As Ben said, you could map any drive. Heck, you could have mapped Q: to the dlls/inetmib1/tests directory and the inetmib1 test would have worked, while having no mapping would not work. --Juan

May 3, 2009

Re: RFC on Base Wine Config

by chris ahrendt

Ben Klein wrote: > 2009/5/3 chris ahrendt <celticht32(a)yahoo.com>: > >> I have noticed something with reporting bugs and problems that are >> encountered... >> >> If the user is allowed to delete the Z: share to / once this is done >> things start acting strange or not working. >> > > In general, you can't run apps outside of what's linked to in > dosdevices. You certainly can't launch them from inside Wine. The link > to / is mostly there for convenience so you don't have to keep dumping > downloads (e.g. patches or small installers) in ~/.wine/drive_c every > time you want to install them, and partly to allow Wine to launch > applications in /usr/bin et al (e.g. winebrowser). > > >> Many people have done this for various reasons. >> > > Yes, and it's valid to do so. > > >> My suggestion is to do the following: >> >> 1. If we have a base configuration that should not change for settings >> IE the Z: mapping then do not allow this to be changed or deleted in >> winecfg. If someone is dumb enough to go into the ini file and delete it >> then they should know better. >> > > This would make a lot of people unhappy (like the creation of the > Universe) for "various reasons". > > >> 2. If it is critical that the Z: or drive mapping be there for / then >> if its missing should wine then handle this condition? >> > > 1) It's not critical. > 2) Wine already handles this condition. It's no different from any > other drive link in this way. It doesn't even have to be Z; you can > manually change it to be D if you really want. The only critical drive > is C: and that IS handled differently (especially in winecfg). > > > ok then I am very confused then... I deleted the / mapping all together and then ran the dotest script and the make test scripts dotest fails if the / mapping is not there along with the inetmib1 test. I opened a bug concerning the inetmib test failing and was told that my configuration with the / mapping deleted was an invalid wine configuration that the / is absolutely needed by wine. So I am confused... is it required or not? and if it is then we get back to my original RFC here =D Chris

May 3, 2009

Re: RFC on Base Wine Config

by Ben Klein

2009/5/3 chris ahrendt <celticht32(a)yahoo.com>: > > I have noticed something with reporting bugs and problems that are > encountered... > > If the user is allowed to delete the Z: share to / once this is done > things start acting strange or not working. In general, you can't run apps outside of what's linked to in dosdevices. You certainly can't launch them from inside Wine. The link to / is mostly there for convenience so you don't have to keep dumping downloads (e.g. patches or small installers) in ~/.wine/drive_c every time you want to install them, and partly to allow Wine to launch applications in /usr/bin et al (e.g. winebrowser). > Many people have done this for various reasons. Yes, and it's valid to do so. > My suggestion is to do the following: > > 1. If we have a base configuration that should not change for settings > IE the Z: mapping then do not allow this to be changed or deleted in > winecfg. If someone is dumb enough to go into the ini file and delete it > then they should know better. This would make a lot of people unhappy (like the creation of the Universe) for "various reasons". > 2. If it is critical that the Z: or drive mapping be there for / then > if its missing should wine then handle this condition? 1) It's not critical. 2) Wine already handles this condition. It's no different from any other drive link in this way. It doesn't even have to be Z; you can manually change it to be D if you really want. The only critical drive is C: and that IS handled differently (especially in winecfg).

May 3, 2009

RFC on Base Wine Config

by chris ahrendt

I have noticed something with reporting bugs and problems that are encountered... If the user is allowed to delete the Z: share to / once this is done things start acting strange or not working. Many people have done this for various reasons. My suggestion is to do the following: 1. If we have a base configuration that should not change for settings IE the Z: mapping then do not allow this to be changed or deleted in winecfg. If someone is dumb enough to go into the ini file and delete it then they should know better. 2. If it is critical that the Z: or drive mapping be there for / then if its missing should wine then handle this condition? Chris

May 3, 2009

Re: error report

by James McKenzie

Ruben Hillewaere wrote: > Hello, > > > I wanted to install (Dar)wine on my Intel Mac, first I've tried with > the binaries found on http://wiki.winehq.org/MacOSX/Installing The > installation goes fine, but running any of the apps fails. > > So, instead, I've tried to build Wine from Scratch, this is what I get: > > > ruben(a)CakeSlicer:~/distrib$ ./create_darwine_distrib.sh $VERSION > ~/Desktop/wine-$VERSION > # Packaging Darwine for version 1.1.20 using Wine sources in > /Users/ruben/Desktop/wine-1.1.20... > # Building Wine in /Users/ruben/Desktop/wine-1.1.20 (warning: takes a > long time)... > configure: WARNING: mach-o/dyld_images.h: present but cannot be compiled > configure: WARNING: mach-o/dyld_images.h: check for missing > prerequisite headers? > configure: WARNING: mach-o/dyld_images.h: see the Autoconf documentation > configure: WARNING: mach-o/dyld_images.h: section "Present But > Cannot Be Compiled" > configure: WARNING: mach-o/dyld_images.h: proceeding with the > preprocessor's result > configure: WARNING: mach-o/dyld_images.h: in the future, the compiler > will take precedence > configure: WARNING: ## ------------------------------------ ## > configure: WARNING: ## Report this to wine-devel(a)winehq.org ## > configure: WARNING: ## ------------------------------------ ## > configure: error: FreeType development files not found. Fonts will not > be built. > Use the --without-freetype option if you really want this. > ***** Error: Can't build wine > Did you install XCode, the X11SDK from your Leopard disk, and get the required packages from either Fink or MacPorts? You might want to try either: 1. The build environment from Mike Kronenberg's site (it is on the same line as the unstable version), or 2. Install either Fink or MacPorts and use their build system. Either should give you a working Wine for MacOSX. If you have further comments/questions, we are here to help. James McKenzie

May 3, 2009

Re: IE and MSN Messenger 7.0

by Ben Klein

2009/5/1 Remco <remco47(a)gmail.com>: > On Fri, May 1, 2009 at 1:18 AM, Ben Klein <shacklein(a)gmail.com> wrote: >> 2009/5/1 Cissyvonwinckelmann <cissyvonwinckelmann(a)planet.nl>: >>> hartelijk dank Benm ja ik moet snel een andere pc hebben, want dit is een >>> hele ouwe dan krijg je de moeilijkheden, >>> groetjes cissy >>> >> >> I have to use Google Language Tools to translate your text, so I >> apologise if I misunderstand you. > > You did indeed misunderstand him. I'll translate his messages: > > ----- > Hi, > Is there a possibility to still download Messenger 7.0? > You see, I am still running Windows ME. > Waiting for your answer, > Cheers, cissy > ----- > > And his next email: > > ----- > Thank you very much, Ben. Yeah, I must get another PC soon, because > this is an old one and that causes problems. > Cheers, cissy. > ----- > > So I'm pretty sure he's on the wrong mailing list. I'll leave it to you to tell him to go to AppDB and discover MSN Messenger doesn't work well then ;) Or at least go to wine-users and bug them with Google Translate :P

May 3, 2009

Re: Severity levels

by Ben Klein

I really didn't think this one deserved even my comment, but here goes. 2009/5/3 Austin English <austinenglish(a)gmail.com>: > 2009/5/1 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se>: >> Current severity levels are perfect for server applications where everything is simply about functionality working or not working. >> However, the overwhelming majority of windows applications in general, and those being ported through wine in particular are GUI-based, end-user applications. >> When it comes to these kinds of applications, in front of which actual people sit for hours on end doing actual work, other factors come into play. > > Wine is meant to support _ALL_ windows applications. It doesn't give > priority to 'server' or 'desktop' applications (there is no > difference, really), but instead tries to make all of them work. > > I have a feeling that by 'server' applications, you meant to say 'old > crappy business applications', or something similar, which makes a bit > of sense. Those applications are simple, and don't depend on a large > portion of the Win32 API, which makes them easy to get running. I have a feeling that by "server" applications, he meant stuff that's not Wine. For me, games and regular applications running in Wine is still "simply about functionality working or not working". It's still a matter of determining how much a bug affects the functionality, whether that's gameplay, graphics, HID responsiveness ... 2009/5/3 Austin English <austinenglish(a)gmail.com>: > 2009/5/2 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se>: >> Not applications, issues. >> My point is that user experience issues gets a lower severity than they should. >> Let's take photoshop CS 4 with two old but relevant actual issues as an example. >> 1. There is a problem with the text tool functionality, it did not work. Everything else works, though. "Text tool" is one tool out of many. "Minor" loss of functionality. "Normal" at worst. >> 2. There are serious graphics problems, huge artifacts, the entire application is almost unworkable under Gnome. If it's restricted to a small number of applications, "Normal". If it's a reasonably large number, "Major". Regardless of what you might think, it's not JUST a "UI glitch" if it seriously impairs functionality. Even the use of the word "serious" in your description implies it's more than a "Minor" bug. >> With the current severity levels(without common sense), example 1 gets higher priority, which I think is wrong. Without common sense, all bug reports would be "Enhancement" requests, or "Critical", depending on how arrogant the reporter is. Common sense must *always* be applied. > The problem is, however, that many of those problems only break an > application or two. What is a blocker for Photoshop isn't a blocker > for World of Warcraft or Microsoft Office, for example. Hence the bug is "Normal" and not "Major". > Please bottom post on wine mailing lists. Oh, and use "Reply to all" so you stop just hitting Austin with responses! 2009/5/3 Rosanne DiMesio <dimesio(a)earthlink.net>: > On Sat, 2 May 2009 21:08:23 +0200 > Nicklas Börjesson <Nicklas.Borjesson(a)ws.se> wrote: >> Non-technical? Posting on and following the wine-devel list? Severity levels perfectly clear? >> I must say, you've got some serious credibility issues.. :-) Rosanne is an AppDB admin. What contribution have you made to Wine? Out of you and her, I don't think her credibility can be called in to question. And before you ask, I'm also an AppDB admin, I package the Debian packages for WineHQ, and have had a patch committed to Wine. I'll even send you the git revision code if you can't find it! :D Note that like Rosanne, even when I was a newbie submitting bug reports, I understood the severity levels because I read the descriptions. The descriptions are fine as is, with the possible exception of "Blocker" (people submit "Blocker" bugs for "Normal" issues because it blocks the thing that they're doing).

May 3, 2009

Re: Giving up for now

by Ben Klein

2009/5/3 Joel Holdsworth <joel(a)airwebreathe.org.uk>: > On Sat, 2009-05-02 at 22:56 +0200, Roderick Colenbrander wrote: >> Why again did you need this specific alphablend method? The icon can't >> be converted to use some basic color keying for transparency or so? > > The reason is that the outlines will look aliased, and there will be no > drop-shadows - without alpha the Tango icons won't look better than the > current set. Also, I figured that icon rendering should be fixed for the > sake of wine as a whole - which I think it should. It seems like a good > little task for a wine beginner, and indeed I've made a lot of progress > - I'm just a bit stuck. > > The culprit is a transfer through StretchDIBits in user32 which strips > the alpha channel. I can't see a way round it - using StretchBlt doesn't > help, and neither does GdiTransparentBlt. > > Another insentive: I suspect fixing this would also fix bug #201 which > is now over 8 years old! What format are your Tango icons in? Are you converting them to .ICO files as you go, or leaving them in PNG/some other known alpha channel supporting format?

May 3, 2009

Re: Giving up for now

by Joel Holdsworth

On Sat, 2009-05-02 at 22:56 +0200, Roderick Colenbrander wrote: > On Sat, May 2, 2009 at 8:57 PM, Joel Holdsworth > <joel(a)airwebreathe.org.uk> wrote: > > On Sat, 2009-05-02 at 20:38 +0200, Roderick Colenbrander wrote: > >> On Sat, May 2, 2009 at 6:55 PM, Joel Holdsworth > >> <joel(a)airwebreathe.org.uk> wrote: > >> > Hi All, > >> > > >> > I've hit a bit of a wall with alpha blended icons. CreateIcon is working > >> > fine for icon creation, but ExtractIcon and LoadIconFromResource etc. > >> > are all proving more of a problem. All of these use various GDI DIB > >> > functions to coerce the icon bitmap to the correct colour depth and > >> > size. The problem is that preserving the alpha channel through these DIB > >> > functions seems to be impossible because they go via X11, so until the > >> > dib engine is merged (after hell freezes over) I'm not sure I can go > >> > much further. > >> > > >> > Joel > >> > > >> > > >> > > >> > > >> > > >> > >> If you say X11 might be problematic note that more and more display > >> drivers are offering visuals with alpha, so 32-bit ones instead of > >> 24-bit. You could force the selection of such a visual in winex11.drv > >> for testing. > >> > >> Roderick > > > > Is that right? I simply assumed it would screw it up. If the problem can > > be solved with fixes to user32 or gdi32, then I can probably find the > > solution. If it involves work on winex11, then I'm not really the right > > guy for the job. > > > > > > > > Why again did you need this specific alphablend method? The icon can't > be converted to use some basic color keying for transparency or so? The reason is that the outlines will look aliased, and there will be no drop-shadows - without alpha the Tango icons won't look better than the current set. Also, I figured that icon rendering should be fixed for the sake of wine as a whole - which I think it should. It seems like a good little task for a wine beginner, and indeed I've made a lot of progress - I'm just a bit stuck. The culprit is a transfer through StretchDIBits in user32 which strips the alpha channel. I can't see a way round it - using StretchBlt doesn't help, and neither does GdiTransparentBlt. Another insentive: I suspect fixing this would also fix bug #201 which is now over 8 years old!

May 2, 2009

Re: Giving up for now

by Roderick Colenbrander

On Sat, May 2, 2009 at 8:57 PM, Joel Holdsworth <joel(a)airwebreathe.org.uk> wrote: > On Sat, 2009-05-02 at 20:38 +0200, Roderick Colenbrander wrote: >> On Sat, May 2, 2009 at 6:55 PM, Joel Holdsworth >> <joel(a)airwebreathe.org.uk> wrote: >> > Hi All, >> > >> > I've hit a bit of a wall with alpha blended icons. CreateIcon is working >> > fine for icon creation, but ExtractIcon and LoadIconFromResource etc. >> > are all proving more of a problem. All of these use various GDI DIB >> > functions to coerce the icon bitmap to the correct colour depth and >> > size. The problem is that preserving the alpha channel through these DIB >> > functions seems to be impossible because they go via X11, so until the >> > dib engine is merged (after hell freezes over) I'm not sure I can go >> > much further. >> > >> > Joel >> > >> > >> > >> > >> > >> >> If you say X11 might be problematic note that more and more display >> drivers are offering visuals with alpha, so 32-bit ones instead of >> 24-bit. You could force the selection of such a visual in winex11.drv >> for testing. >> >> Roderick > > Is that right? I simply assumed it would screw it up. If the problem can > be solved with fixes to user32 or gdi32, then I can probably find the > solution. If it involves work on winex11, then I'm not really the right > guy for the job. > > > Why again did you need this specific alphablend method? The icon can't be converted to use some basic color keying for transparency or so?

May 2, 2009

RE: Severity levels

by Nicklas Börjesson

>I think "middle-aged college English teacher who couldn't code if her life depended on it" counts as non-technical. :-) The only thing that sets me >apart from most users is the fact that I actually do RTFM, but that's just because I'm one of those eccentric academics who thinks reading is a >really good way to learn. Reading? But you are going to end up all cross-eyed, dear? Everything I know about programming I have learned from stories my parents told me as a kid. And they heard them from their parents and now I am passing it on to my 3-year old daughter. She is very much into the older Windows API:s right now and just wants to hear that story about oleacc.dll again and again and again.

May 2, 2009

Re: Severity levels

by Rosanne DiMesio

On Sat, 2 May 2009 21:08:23 +0200 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se> wrote: > > Non-technical? Posting on and following the wine-devel list? Severity levels perfectly clear? > I must say, you've got some serious credibility issues.. :-) > > I think "middle-aged college English teacher who couldn't code if her life depended on it" counts as non-technical. :-) The only thing that sets me apart from most users is the fact that I actually do RTFM, but that's just because I'm one of those eccentric academics who thinks reading is a really good way to learn. -- Rosanne DiMesio <dimesio(a)earthlink.net>

May 2, 2009

RE: Severity levels

by Nicklas Börjesson

>The problem is, however, that many of those problems only break an >application or two. What is a blocker for Photoshop isn't a blocker >for World of Warcraft or Microsoft Office, for example. You mean because Photoshop often use the more obscure parts of the APIs? Otherwise bugs in GUI shouldn't be less contagious than other kinds. Unless one regards UE issues as less severe, that is... :-) Anyway, I fail to see how this connects to the severity level discussion? >Please bottom post on wine mailing lists. Yep. But I was top posted earlier so I got confused. Also I am in a crappy exchange web mail client.. I hope you managed to read this post better. //Nicklas

May 2, 2009

Re: Severity levels

by Austin English

2009/5/2 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se>: > Not applications, issues. > My point is that user experience issues gets a lower severity than they should. > Let's take photoshop CS 4 with two old but relevant actual issues as an example. > 1. There is a problem with the text tool functionality, it did not work. Everything else works, though. > 2. There are serious graphics problems, huge artifacts, the entire application is almost unworkable under Gnome. > > With the current severity levels(without common sense), example 1 gets higher priority, which I think is wrong. > > //Nicklas > > PS. > Yes I know the actual issue turned out to be a configuration thing. But that's not the point. > DS. The problem is, however, that many of those problems only break an application or two. What is a blocker for Photoshop isn't a blocker for World of Warcraft or Microsoft Office, for example. Please bottom post on wine mailing lists. -- -Austin

May 2, 2009

RE: Severity levels

by Nicklas Börjesson

Not applications, issues. My point is that user experience issues gets a lower severity than they should. Let's take photoshop CS 4 with two old but relevant actual issues as an example. 1. There is a problem with the text tool functionality, it did not work. Everything else works, though. 2. There are serious graphics problems, huge artifacts, the entire application is almost unworkable under Gnome. With the current severity levels(without common sense), example 1 gets higher priority, which I think is wrong. //Nicklas PS. Yes I know the actual issue turned out to be a configuration thing. But that's not the point. DS. -----Original Message----- From: Austin English [mailto:austinenglish(a)gmail.com] Sent: Sat 2009-05-02 20:56 To: Nicklas Börjesson Cc: wine-devel(a)winehq.org Subject: Re: Severity levels 2009/5/2 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se>: >>Wine is meant to support _ALL_ windows applications. It doesn't give >>priority to 'server' or 'desktop' applications (there is no >>difference, really), but instead tries to make all of them work. > > Yes, but I wasn't talking about server applikations per se, but that the severity levels would be perfect for a server application, hence skewing the priorities away from GUI and other, more "soft", user experience issues. I'm curious what non-gui applications you're talking about in regards to wine. -- -Austin

May 2, 2009

RE: Severity levels

by Nicklas Börjesson

The normal user doesn't even understand that the definitions should be read, most people think they know what "trivial", "minor","normal","major" means anyway. I actually discussed this with some friends recently. I just think that it could be more user-oriented. Non-technical? Posting on and following the wine-devel list? Severity levels perfectly clear? I must say, you've got some serious credibility issues.. :-) //Nicklas -----Original Message----- From: Rosanne DiMesio [mailto:dimesio(a)earthlink.net] Sent: Sat 2009-05-02 19:09 To: Ken Sharp Cc: Nicklas Börjesson; wine-devel(a)winehq.org Subject: Re: Severity levels > > This is way easier to understand for normal people. Speaking as a non-technical user who does file bug reports now and then, I have always found the definitions of the severity levels to be perfectly clear, even when I was new to Wine, and from what I've seen, when a reporter sets the wrong severity level, it's usually because they didn't bother to read the definitions in the first place. -- Rosanne DiMesio <dimesio(a)earthlink.net>

May 2, 2009

RE: Question about my user32 tests patch

by Ge van Geldorp

Hi Joel, > From: Joel Holdsworth <joel(a)airwebreathe.org.uk> > > How do you deal with this problem, because presumably not every test > contributor has VMs ready to confirm the behaviour of 95, 98, ME, 2000, > XP and Vista. Do I submit the patch as-is, in the knowlege that it will > cause failures in old windows? Presumably not - so what do you suggest I > do? I have a whole bunch of VMs set up specifically for Wine testing, so feel free to send me patches you think might behave differently on different Windows versions. One caveat: I personally stopped caring about 9x when Win2000 came out, so I'm not testing on those versions. The good (but unsurprising) news is that your new tests pass on all my XP (4 different configurations) and Win2k3 (also 4 different configurations) machines. I don't see failures on NT4, but perhaps the test was skipped there? The bad news is they failed on W2k, Vista and Win2k8. I've attached the test reports for all failures. Ge.

May 2, 2009

Re: Giving up for now

by Joel Holdsworth

On Sat, 2009-05-02 at 20:38 +0200, Roderick Colenbrander wrote: > On Sat, May 2, 2009 at 6:55 PM, Joel Holdsworth > <joel(a)airwebreathe.org.uk> wrote: > > Hi All, > > > > I've hit a bit of a wall with alpha blended icons. CreateIcon is working > > fine for icon creation, but ExtractIcon and LoadIconFromResource etc. > > are all proving more of a problem. All of these use various GDI DIB > > functions to coerce the icon bitmap to the correct colour depth and > > size. The problem is that preserving the alpha channel through these DIB > > functions seems to be impossible because they go via X11, so until the > > dib engine is merged (after hell freezes over) I'm not sure I can go > > much further. > > > > Joel > > > > > > > > > > > > If you say X11 might be problematic note that more and more display > drivers are offering visuals with alpha, so 32-bit ones instead of > 24-bit. You could force the selection of such a visual in winex11.drv > for testing. > > Roderick Is that right? I simply assumed it would screw it up. If the problem can be solved with fixes to user32 or gdi32, then I can probably find the solution. If it involves work on winex11, then I'm not really the right guy for the job.

May 2, 2009

Re: Severity levels

by Austin English

2009/5/2 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se>: >>Wine is meant to support _ALL_ windows applications. It doesn't give >>priority to 'server' or 'desktop' applications (there is no >>difference, really), but instead tries to make all of them work. > > Yes, but I wasn't talking about server applikations per se, but that the severity levels would be perfect for a server application, hence skewing the priorities away from GUI and other, more "soft", user experience issues. I'm curious what non-gui applications you're talking about in regards to wine. -- -Austin

May 2, 2009

RE: Severity levels

by Nicklas Börjesson

>Wine is meant to support _ALL_ windows applications. It doesn't give >priority to 'server' or 'desktop' applications (there is no >difference, really), but instead tries to make all of them work. Yes, but I wasn't talking about server applikations per se, but that the severity levels would be perfect for a server application, hence skewing the priorities away from GUI and other, more "soft", user experience issues. I am not specifically talking about Photoshop, either. I am talking about all GUI-centered applications. Yes, I read about that, huge kudos to Google for still being benevolent(and Dan of course). But. Listen. I am not here to try and get Photoshop CS 4 fixed, that's already done, it works great for me. It's just that I have some ideas on what I would think would be simple but effective changes of the bug reporting and don't give up easily. :-) //Nicklas

May 2, 2009

Re: Giving up for now

by Roderick Colenbrander

On Sat, May 2, 2009 at 6:55 PM, Joel Holdsworth <joel(a)airwebreathe.org.uk> wrote: > Hi All, > > I've hit a bit of a wall with alpha blended icons. CreateIcon is working > fine for icon creation, but ExtractIcon and LoadIconFromResource etc. > are all proving more of a problem. All of these use various GDI DIB > functions to coerce the icon bitmap to the correct colour depth and > size. The problem is that preserving the alpha channel through these DIB > functions seems to be impossible because they go via X11, so until the > dib engine is merged (after hell freezes over) I'm not sure I can go > much further. > > Joel > > > > > If you say X11 might be problematic note that more and more display drivers are offering visuals with alpha, so 32-bit ones instead of 24-bit. You could force the selection of such a visual in winex11.drv for testing. Roderick

May 2, 2009

Re: Severity levels

by Austin English

2009/5/1 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se>: > Current severity levels are perfect for server applications where everything is simply about functionality working or not working. > However, the overwhelming majority of windows applications in general, and those being ported through wine in particular are GUI-based, end-user applications. > When it comes to these kinds of applications, in front of which actual people sit for hours on end doing actual work, other factors come into play. Wine is meant to support _ALL_ windows applications. It doesn't give priority to 'server' or 'desktop' applications (there is no difference, really), but instead tries to make all of them work. I have a feeling that by 'server' applications, you meant to say 'old crappy business applications', or something similar, which makes a bit of sense. Those applications are simple, and don't depend on a large portion of the Win32 API, which makes them easy to get running. While getting Photoshop to run perfectly would be great (and _a lot_ of work has been done for this, by Dan K filing a ton of bugs, and Google funding a lot of bug fixing (http://google-opensource.blogspot.com/2008/02/google-sponsors-wine-improvem…) A lot of that helped CS 3/4, as well, but Adobe also added more complexity, so they don't work quite as well. Remember, Wine is open source, and most developers aren't paid. If you've got a bug that drives you crazy, study the source (http://source.winehq.org/git/wine.git/) and submit a patch (http://wiki.winehq.org/SubmittingPatches) -- -Austin

May 2, 2009

RE: Severity levels

by Nicklas Börjesson

Ok, I have made better posts. >> 1. Blocker "Blocks development and/or testing work" >> >> - Is this even possible? >Yes. I am sorry. Of course it is possible to have these problems. I thought it meant that it blocks ALL development and/or testing work(since it is above critical). In the list, there are mostly platform-specific issues. My mistake. >> 2. Critical "Critical problem that prevents all applications from working" >> >> - Possible, if everyone stopped testing code completely, and also unlikely to be reported by a user. >No, critical bugs are usually opened by non-Linux users. Here I did search, and actually, most bugs have "linux" as an operating system so I couldn't come to that conclusion. Anyway, I get your point. Still don't really see why this is a separate severity level, though. Wouldn't this be a "wineloader" component or something? >> 3. Major "Major loss of functionality for a wide range of applications >> >> - Isn't this just all bugs that has more than $arbitrary_number of applications linked to them? An aggregate, >> rather than a level? >No, it's actually what it say, a WIDE RANGE of applications. Ok..I just thought that "wide range" could be translated into a number or percentage instead of an expression. I thought the opposite way...but couldn't possibly all bugs in wine affect a wide range of appliacations? > Bugzilla is to track bugs, it's not a user support forum, and the bugs > should be classified as the dev's want them to be classified. No, I know it is not a support forum(Is users using is as such a big problem?). But it is nevertheless an interface towards the users of wine. A place they go to when all else has failed(hopefully). And as such it is utterly confusing(for them) and already leads to pointless misunderstandings and frustrations regarding, for example, the severity flag. Anyway. I can't help but feel that we are on completely different pages in many ways. I think that the users should have quite a say with regards to how important a bug is, because for every user putting in the (considerable for a user) effort of reporting a bug, there are dozens that don't say anything at all. In wine's case, because of it's size, this might actually be hundreds. It's badwill. So currently, there is no way at all for users to influence these priorities. To me, user priorities would be a considerable factor, obviously not the only one, but considerable. I know that wine, to a large extent, Is maintained by unpaid individuals(like myself) that want to prioritize themselves. I don't want to take that right away from them, I just feel that it's bad practice to disregard the users' priorities. //Nicklas PS. >Your line length needs fixing. I have to admit I sent this using my employers horrible web mail (no idea why it says 6.5 though, think it is 2005). We will pretty soon "exchange" it, though. :-) DS.

May 2, 2009

Re: Implement gdiplus.dll.GdipSetPathGradientPresetBlend

by Vincent Povirk

> +GpStatus WINGDIPAPI GdipSetPathGradientPresetBlend(GpPathGradient *brush, GDIPCONST REAL *blend, > + GDIPCONST REAL *pos, INT count) The types here don't match MSDN: http://msdn.microsoft.com/en-us/library/ms534047(VS.85).aspx

May 2, 2009

FYI: First running winelib64-port!!!

by André Hentschel

Hi, afer playing around with about 20 source-codes of open-source-project it got one compiled as winelib64-app(and also as 32-Bit winelib-app). It is WinVi 2.99 (http://www.winvi.de) The only difference i found between the original build and my two winelib builds are some GUI-specific things. Tomorrow i will have a look where to write something down about that in the wiki. As i already wrote, PuTTY compiles as winelib64-app, too, but it doesn't run. That's the reason why i called WinVi the first winelib64-app. Best regards André Hentschel

May 2, 2009

Re: Severity levels

by Rosanne DiMesio

> > This is way easier to understand for normal people. Speaking as a non-technical user who does file bug reports now and then, I have always found the definitions of the severity levels to be perfectly clear, even when I was new to Wine, and from what I've seen, when a reporter sets the wrong severity level, it's usually because they didn't bother to read the definitions in the first place. -- Rosanne DiMesio <dimesio(a)earthlink.net>

May 2, 2009

Giving up for now

by Joel Holdsworth

Hi All, I've hit a bit of a wall with alpha blended icons. CreateIcon is working fine for icon creation, but ExtractIcon and LoadIconFromResource etc. are all proving more of a problem. All of these use various GDI DIB functions to coerce the icon bitmap to the correct colour depth and size. The problem is that preserving the alpha channel through these DIB functions seems to be impossible because they go via X11, so until the dib engine is merged (after hell freezes over) I'm not sure I can go much further. Joel

May 2, 2009

Re: Question about my user32 tests patch

by Joel Holdsworth

On Sat, 2009-05-02 at 08:58 -0700, Juan Lang wrote: > Hi Joel, > > > How do you deal with this problem, because presumably not every test > > contributor has VMs ready to confirm the behaviour of 95, 98, ME, 2000, > > XP and Vista. Do I submit the patch as-is, in the knowlege that it will > > cause failures in old windows? Presumably not - so what do you suggest I > > do? > > That's what we generally end up doing. Watching test.winehq.org for > test results once a patch gets committed, or waiting for an email from > someone who watches the results, is a way to get feedback on test > failures on other platforms. > > The alternative is to ask someone to test your tests on other > platforms, by asking on wine-devel as you've done. > > Cheers, > --Juan Ahh ok that's good news!

May 2, 2009

Re: Question about my user32 tests patch

by Juan Lang

Hi Joel, > How do you deal with this problem, because presumably not every test > contributor has VMs ready to confirm the behaviour of 95, 98, ME, 2000, > XP and Vista. Do I submit the patch as-is, in the knowlege that it will > cause failures in old windows? Presumably not - so what do you suggest I > do? That's what we generally end up doing. Watching test.winehq.org for test results once a patch gets committed, or waiting for an email from someone who watches the results, is a way to get feedback on test failures on other platforms. The alternative is to ask someone to test your tests on other platforms, by asking on wine-devel as you've done. Cheers, --Juan

May 2, 2009

Re: Severity levels

by Ken Sharp

Nicklas Börjesson wrote: > I am not sure that common sense is the issue. I think it is a question of who you are and what you know. > Among the ones submitting bugs now is a quickly rising percentage of normal-to-advanced end users, and that percentage is likely to rise even further, as Linux adoption rates increase. 10 million desktops is the last number I've heard..and people are learning how to report problems. Hell, my mom(77 years old) reported a bug a while ago. > > My point is, why not adapt the severity levels to the competence level of the submitters instead of having to correct them all the time, creating badwill? > > Can't the three highest severity levels just be removed? Are they relevant? > > 1. Blocker "Blocks development and/or testing work" > > - Is this even possible? Yes. http://bugs.winehq.org/buglist.cgi?query_format=advanced&short_desc_type=al… > > 2. Critical "Critical problem that prevents all applications from working" > > - Possible, if everyone stopped testing code completely, and also unlikely to be reported by a user. No, critical bugs are usually opened by non-Linux users. > > 3. Major "Major loss of functionality for a wide range of applications > > - Isn't this just all bugs that has more than $arbitrary_number of applications linked to them? An aggregate, rather than a level? No, it's actually what it say, a WIDE RANGE of applications. > > > Then, the severity(or "impact") levels could be: > > Critical > High > Medium > Low > > This is way easier to understand for normal people. > Also, the definition of each level should not be all that clear(except maybe critical) either, the levels will be discussed anyway, so it is easier to motivate for the developers to grade down a bug without too much discussion. Because the more people start using wine to actually make a living, the more important it will be to them. > One would think that vague levels would create more discussion, but according to my experience, and with end-users, it seems to work the other way. > > And yes, I know that the bug reporting system is used by the developers internally as well, but do you really use the first two levels so often that you need them(I hope not)? As above. Searching for critical bugs would have answered that question. http://bugs.winehq.org/buglist.cgi?query_format=advanced&short_desc_type=al… Bugzilla is to track bugs, it's not a user support forum, and the bugs should be classified as the dev's want them to be classified. That's what this is for: http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity Normal: For an application crash or loss of functionality UI glitch or not, if you can't use an app, you can't use it. This is common sense. > > //Nicklas > > Your line length needs fixing. "Produced By Microsoft Exchange V6.5" This is why.

May 2, 2009

RE: Severity levels

by Nicklas Börjesson

I am not sure that common sense is the issue. I think it is a question of who you are and what you know. Among the ones submitting bugs now is a quickly rising percentage of normal-to-advanced end users, and that percentage is likely to rise even further, as Linux adoption rates increase. 10 million desktops is the last number I've heard..and people are learning how to report problems. Hell, my mom(77 years old) reported a bug a while ago. My point is, why not adapt the severity levels to the competence level of the submitters instead of having to correct them all the time, creating badwill? Can't the three highest severity levels just be removed? Are they relevant? 1. Blocker "Blocks development and/or testing work" - Is this even possible? 2. Critical "Critical problem that prevents all applications from working" - Possible, if everyone stopped testing code completely, and also unlikely to be reported by a user. 3. Major "Major loss of functionality for a wide range of applications - Isn't this just all bugs that has more than $arbitrary_number of applications linked to them? An aggregate, rather than a level? Then, the severity(or "impact") levels could be: Critical High Medium Low This is way easier to understand for normal people. Also, the definition of each level should not be all that clear(except maybe critical) either, the levels will be discussed anyway, so it is easier to motivate for the developers to grade down a bug without too much discussion. Because the more people start using wine to actually make a living, the more important it will be to them. One would think that vague levels would create more discussion, but according to my experience, and with end-users, it seems to work the other way. And yes, I know that the bug reporting system is used by the developers internally as well, but do you really use the first two levels so often that you need them(I hope not)? //Nicklas

May 2, 2009

Re: FYI: 64-Bit Winelib-compilation

by André Hentschel

Austin English schrieb: > 2009/5/1 André Hentschel <nerv(a)dawncrow.de>: > >> To my suprise it didnt run. >> > > Interesting...does it run as a 32-bit winelib app? Have you tried > compiling it with 64-bit mingw and seeing if it works there? > > i have problems compiling it with mingw64, because i am not familiar with it. would someone else try it?

May 2, 2009

Re: [shell32] stub for ExtractVersionResource16W

by Stefan Leichter

Am Saturday 02 May 2009 12:54:14 schrieb Dmitry Timoshkov: > "Stefan Leichter" <Stefan.Leichter(a)camline.com> wrote: > > +/*********************************************************************** > > + * ExtractVersionResource16W (SHELL32.@) > > + */ > > +BOOL WINAPI ExtractVersionResource16W(LPWSTR s, DWORD d) { > > + FIXME("(%s %x) stub!\n", debugstr_w(s), d); > > + return FALSE; > > +} > > Please follow the braces placement style of the file. > > Also you might be interested that according to > http://www.geoffchappell.com/viewer.htm?doc=studies/windows/shell/shell32/h >istory/names351.htm ExtractVersionResource16W is discontinued starting from > Windows Vista. What does the second point means for wine? -- Stefan

May 2, 2009

Re: Severity levels

by Ken Sharp

The severity levels are there for guidance. I would hope that common sense would prevail, but clearly it doesn't. If a UI glitch makes a program unusable, then it's normal. I can not believe you need this pointing out to you. http://bugs.winehq.org/show_bug.cgi?id=1347 "Screen is wiped/blanked on usage of DirectDraw (black screen/desktop)" = UI glitch = Sev. Normal Common sense people, that's all that is asked.

May 2, 2009

Question about my user32 tests patch

by Joel Holdsworth

Hi All, I just submitted my first ever patch to wine-patches (attached) - good news. In retrospect I may have been a little premature. The patch adds tests for user32:DrawIcon and user32:DrawIconEx including tests for icon alpha blending which wine does not currently support. It occured to me that my alpha tests will fail in versions of Windows that don't support alpha blending - but the problem is I'm not sure at what point alpha began to be supported. I only have a VM for XP - and I think, but I don't know for sure, that alpha icons began to be supported in 2000. How do you deal with this problem, because presumably not every test contributor has VMs ready to confirm the behaviour of 95, 98, ME, 2000, XP and Vista. Do I submit the patch as-is, in the knowlege that it will cause failures in old windows? Presumably not - so what do you suggest I do? I now have code to make DrawIcon pass the alpha tests, and I'm hoping to have DrawIconEx ready in a few hours. With these done it should be possible to in-cooperate my Tango patches, which should improve the appearance of wine quite substantially. Thanks Joel

May 2, 2009

Re: [shell32] stub for ExtractVersionResource16W

by Dmitry Timoshkov

"Stefan Leichter" <Stefan.Leichter(a)camline.com> wrote: > +/*********************************************************************** > + * ExtractVersionResource16W (SHELL32.@) > + */ > +BOOL WINAPI ExtractVersionResource16W(LPWSTR s, DWORD d) { > + FIXME("(%s %x) stub!\n", debugstr_w(s), d); > + return FALSE; > +} Please follow the braces placement style of the file. Also you might be interested that according to http://www.geoffchappell.com/viewer.htm?doc=studies/windows/shell/shell32/h… ExtractVersionResource16W is discontinued starting from Windows Vista. -- Dmitry.

May 2, 2009

Re: Severity levels

by Jerome Leclanche

Outside Major/Critical/Enhancement, I don't think severity useful, to be honest. Problem is, more often than not, a minor implementation glitch can result into an application breaking all around if it relies on it a lot. Which is pretty much the case with photoshop at the moment. Maybe it should be renamed to "impact", or something that would present itself differently to a first-time user. Or add a second severity field. I don't know, not my call. 2009/5/1 Nicklas Börjesson <Nicklas.Borjesson(a)ws.se>: > Hi all! > > First, I couldn't find any list more suitable than this one to comment the severity levels in the bug reporting so I post it here. If this was a really bad thing to do, please tell me were to do so. > Secondly, don't take this wrong, I am not here to preach, I actually think this is a serious problem. I am not drunk either. Currently. :-) > > So, with regards to severity levels: > > Current severity levels are perfect for server applications where everything is simply about functionality working or not working. > However, the overwhelming majority of windows applications in general, and those being ported through wine in particular are GUI-based, end-user applications. > When it comes to these kinds of applications, in front of which actual people sit for hours on end doing actual work, other factors come into play. > > So I would like to introduce a bold new weight into the severity assessment: The user experience. Or at least the bugs' negative impact on it. > The user experience(UE from here on) is really quite impossible to quantify exactly, luckily that is not usually necessary. > > There are several reasons to incorporate this into the severity classification, but I'll stop at two: > > 1. The ones reporting the bugs will come across with how severe they think the bug is to them. > Currently, there is far too much of "you've got a almost black screen or black square instead of icons running Photoshop?..hmm that's really trivial...an 'UI glitch', but OK then, I'll mark it minor to be nice to ya." > To a user, even an advanced one, this must feel like talking to a condescending Martian. Frustrating, if not infuriating. > Likely, they will never again take the time to make a bug report. It is even quite likely that they will give up their move away from windows. > > 2. Currently, fixing a "trivial" UE-bug can make way more users happy than fixing a "normal" functionality-bug. > This means that bug fixing is prioritized on a basis other than catering to the users needs. And to me, that's something that really shows. > Can one defend this without invalidating the wine project? > It is a serious question, I might have missed something fundamental. > > Anyway, I have some ideas on how to make the severity classifications better(and more intuitive for the mere user), but I won't go in to that now. > I just want to know if any of you agree with me. Do I make a valid point? > > //Nicklas > > PS. > I repost this since I didn't get any post from the server the first time. > Also I expect this post to piss some off, which makes it even stranger not to get any replies at all. > BTW, I also just read in a comment in a bug report that the severity flag doesn't mean much at all when it comes to how a bug is prioritized. > So the only input the users have on how important a bug is to them is practically ignored? Why have that checkbox then? > And why make such a big thing of it not being correctly set? > DS. > > > > -- Adys

May 2, 2009

Re: Wine fundraising idea

by Scott Ritchie

Austin English wrote: > Howdy, > > I was reading through a GSoC thread on how people are spending their > coding money. Someone posted that they thought people should donate to > miro, the internet HDTV player. They've got a pretty neat donation > scheme, where people can 'adopt' a line of code, and get updates on > it, etc. Pretty neat: > https://www.getmiro.com/adopt/ > > Just food for thought, for those of y'all wanting to add $ to the > WineHQ coffers, for WineConf, or what not (*cough* test/compile farm > *cough*). > This is functionally similar to asking for people to become members of some sort of foundation (eg monthly or annual contribution). It's a funding model that works, which is why they do it for public radio. I think there's real potential here. Thanks, Scott Ritchie

May 2, 2009

Re: msi/tests: Fix MsiApplyMultiplePatches tests on Windows.

by Juan Lang

Hi Nicolas, - ok(DeleteFileA("lithium.txt"), "Expected lithium.txt to exist\n"); + ok(DeleteFileA("lithium.txt"), "Expected lithium.txt to exist\n"); Please don't include whitespace-only changes in your patch. - + Same here. Thanks, --Juan

May 1, 2009

Re: user32: combine horizontal and vertical window scroll bar info in a single structure.

by Alexandre Julliard

Rein Klazes <wijn(a)online.nl> writes: > What is already in the tests: > > 1) You need the alloc flag for instance when SetScrollInfo or > SetScrollRange is called on a window without the WS_[HV]SCROLL styles. I > can add a test that shows that the window styles remain unchanged when > eg. SetScrollInfo creates the scrollinfo. > > 2) You need the style test when testing GetScrollInfo and GetScrollRange > on windows with WS_[HV]SCROLL styles. > > Now the alloc flag may not be specified correctly in the other cases > Additional tests to see whether the alloc flag is correctly passed for > [GS}etScrollBarInfo and EnableScrollBar can be added. > > Would such tests address your concerns? No, what you'd need is a test that shows that calling a function that doesn't create a scrollbar (alloc=FALSE) suddenly starts to create one if WS_[HV]SCROLL is set. To test this meaningfully you'd need to set the style by hand, not at window creation. -- Alexandre Julliard julliard(a)winehq.org

May 1, 2009

Re: FYI: 64-Bit Winelib-compilation

by André Hentschel

Austin English schrieb: > 2009/5/1 André Hentschel <nerv(a)dawncrow.de>: > >> To my suprise it didnt run. >> > > Interesting...does it run as a 32-bit winelib app? Have you tried > compiling it with 64-bit mingw and seeing if it works there? > > Putty runs as 32-bit winelib app. The test with mingw64 i will try next days.

May 1, 2009

Re: FYI: 64-Bit Winelib-compilation

by Austin English

2009/5/1 André Hentschel <nerv(a)dawncrow.de>: > To my suprise it didnt run. Interesting...does it run as a 32-bit winelib app? Have you tried compiling it with 64-bit mingw and seeing if it works there? -- -Austin

May 1, 2009

FYI: 64-Bit Winelib-compilation

by André Hentschel

Hi, these days i got my gcc 4.4 working and first compiled wine64. Next thing i did was to modify winemaker to generate Makefiles for 64-Bit compilation. I first tried something simple and it worked great, so i took my modified Putty-sourcecode and gave it a try. And wow it worked great! Just compiled fine. To my suprise it didnt run. Since todays git, the modified winemaker got in and i hope it might be usefull! Best regards André Hentschel

May 1, 2009

Severity levels

by Nicklas Börjesson

Hi all! First, I couldn't find any list more suitable than this one to comment the severity levels in the bug reporting so I post it here. If this was a really bad thing to do, please tell me were to do so. Secondly, don't take this wrong, I am not here to preach, I actually think this is a serious problem. I am not drunk either. Currently. :-) So, with regards to severity levels: Current severity levels are perfect for server applications where everything is simply about functionality working or not working. However, the overwhelming majority of windows applications in general, and those being ported through wine in particular are GUI-based, end-user applications. When it comes to these kinds of applications, in front of which actual people sit for hours on end doing actual work, other factors come into play. So I would like to introduce a bold new weight into the severity assessment: The user experience. Or at least the bugs' negative impact on it. The user experience(UE from here on) is really quite impossible to quantify exactly, luckily that is not usually necessary. There are several reasons to incorporate this into the severity classification, but I'll stop at two: 1. The ones reporting the bugs will come across with how severe they think the bug is to them. Currently, there is far too much of "you've got a almost black screen or black square instead of icons running Photoshop?..hmm that's really trivial...an 'UI glitch', but OK then, I'll mark it minor to be nice to ya." To a user, even an advanced one, this must feel like talking to a condescending Martian. Frustrating, if not infuriating. Likely, they will never again take the time to make a bug report. It is even quite likely that they will give up their move away from windows. 2. Currently, fixing a "trivial" UE-bug can make way more users happy than fixing a "normal" functionality-bug. This means that bug fixing is prioritized on a basis other than catering to the users needs. And to me, that's something that really shows. Can one defend this without invalidating the wine project? It is a serious question, I might have missed something fundamental. Anyway, I have some ideas on how to make the severity classifications better(and more intuitive for the mere user), but I won't go in to that now. I just want to know if any of you agree with me. Do I make a valid point? //Nicklas PS. I repost this since I didn't get any post from the server the first time. Also I expect this post to piss some off, which makes it even stranger not to get any replies at all. BTW, I also just read in a comment in a bug report that the severity flag doesn't mean much at all when it comes to how a bug is prioritized. So the only input the users have on how important a bug is to them is practically ignored? Why have that checkbox then? And why make such a big thing of it not being correctly set? DS.

May 1, 2009

Re: user32: combine horizontal and vertical window scroll bar info in a single structure.

by Rein Klazes

On Fri, 01 May 2009 13:13:05 +0200, you wrote: >Rein Klazes <wijn(a)online.nl> writes: > >> - if (!infoPtr && alloc) >> + if (!infoPtr && ( alloc || (wndPtr->dwStyle & (WS_VSCROLL | WS_HSCROLL)))) >> { > >This bit doesn't look right, and defeats the purpose of the alloc >flag. It would need some more test cases. The alloc flag is not only set by SCROLL_DrawScrollBar, which may be what you are thinking of here. What is already in the tests: 1) You need the alloc flag for instance when SetScrollInfo or SetScrollRange is called on a window without the WS_[HV]SCROLL styles. I can add a test that shows that the window styles remain unchanged when eg. SetScrollInfo creates the scrollinfo. 2) You need the style test when testing GetScrollInfo and GetScrollRange on windows with WS_[HV]SCROLL styles. Now the alloc flag may not be specified correctly in the other cases Additional tests to see whether the alloc flag is correctly passed for [GS}etScrollBarInfo and EnableScrollBar can be added. Would such tests address your concerns? Rein.

May 1, 2009

Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more

by Michael Stefaniuc

Ben Klein wrote: > 2009/5/1 Susan Cragin <susancragin(a)earthlink.net>: >>> I filed ubuntu bug 369762. >> Ubuntu didn't think much of my bug. They sent me the following recipe to cure it, and marked the bug invalid. >> >> 1) Edit /etc/pulse/client.conf, and change "autospawn = yes" to "autospawn = no" >> 2) `touch $HOME/.pulse_a11y_nostart' >> 3) `asoundconf list' >> 4) choose the desired card from the previous command's output, and use `asoundconf set-default-card CARD', replacing CARD as appropriate >> 5) `killall pulseaudio' >> >> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/348353 >> mentions a recent kernel patch that routes all audio through pulse. I wonder if this patch is the culprit? > > It mentions a patch, not a kernel patch. I'd be *very* surprised if > there was anything kernel-side specifically routing audio through There is a kernel patch to reroute character devices to user space; afair that patch is already in. The usage example I have seen given for that patch is to reroute /dev/dsp to pulseaudio. > pulse. More plausibly, it could be a libasound2 patch or even just a > hack to asound.conf/.asoundrc. bye michael

May 1, 2009

Re: Wine fundraising idea

by James Mckenzie

Austin English <austinenglish(a)gmail.com> >Sent: May 1, 2009 12:39 PM >To: Wine Devel <wine-devel(a)winehq.org> >Subject: Wine fundraising idea > >Howdy, > +1 James McKenzie

May 1, 2009

Wine fundraising idea

by Austin English

Howdy, I was reading through a GSoC thread on how people are spending their coding money. Someone posted that they thought people should donate to miro, the internet HDTV player. They've got a pretty neat donation scheme, where people can 'adopt' a line of code, and get updates on it, etc. Pretty neat: https://www.getmiro.com/adopt/ Just food for thought, for those of y'all wanting to add $ to the WineHQ coffers, for WineConf, or what not (*cough* test/compile farm *cough*). -- -Austin

May 1, 2009

Re: Trying buildbot on wine; foiled by distutils expecting mscoree to be resident?

by Dan Kegel

Thanks for the tip about the mscoree access being unimportant. It turns out the pywin32 installer works fine with win2K set, but that doesn't help Twisted_NoDocs-8.2.0.win32-py2.6.exe, which still fails to find win32api. However, if I install ActiveState's python instead of the one from python.org, twisted installs successfully. Now on with the buildbot experiment :-)

May 1, 2009

Re: [resend] shell32: for FO_COPY, if the destination is an empty string, SHFileOperation should use the current directory.

by Juan Lang

Hi Lionel, one minor comment on your patch: + /* If the destination is empty, SHFileOperation should use the current directory. + See bug #13394. */ There's no need to quote the bug to explain why your code is doing what it's doing. The test case is sufficient. --Juan

May 1, 2009

Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more

by Ben Klein

2009/5/1 Susan Cragin <susancragin(a)earthlink.net>: >>I filed ubuntu bug 369762. > > Ubuntu didn't think much of my bug. They sent me the following recipe to cure it, and marked the bug invalid. > > 1) Edit /etc/pulse/client.conf, and change "autospawn = yes" to "autospawn = no" > 2) `touch $HOME/.pulse_a11y_nostart' > 3) `asoundconf list' > 4) choose the desired card from the previous command's output, and use `asoundconf set-default-card CARD', replacing CARD as appropriate > 5) `killall pulseaudio' > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/348353 > mentions a recent kernel patch that routes all audio through pulse. I wonder if this patch is the culprit? It mentions a patch, not a kernel patch. I'd be *very* surprised if there was anything kernel-side specifically routing audio through pulse. More plausibly, it could be a libasound2 patch or even just a hack to asound.conf/.asoundrc.

May 1, 2009

Re: Dib Engine: some update

by Massimo Del Fedele

Luke Benstead ha scritto: > 2009/5/1 Massimo Del Fedele <max(a)veneto.com>: >> Luke Benstead ha scritto: >>> 2009/5/1 Scott Ritchie <scott(a)open-vote.org>: >>>> Massimo Del Fedele wrote: >>>>> I put on bug's 421 page an update of my dib engine. >>>>> It implements AlphaBlend, StretchBlt and has many color fixes. >>>>> If you want to try it, just follow instructions on above page. >>>>> >>>>> Ciao >>>>> >>>>> Max >>>>> >>>> Keep at it, it's very exciting :) >>>> >>>> Thanks, >>>> Scott Ritchie >>>> >>>> >>>> >>> Yeah, nice work Max! You are doing an amazing job, I just wish that we >>> knew how to get it into vanilla Wine! My bro really needs this to move >>> his (and several work) machines to Ubuntu, but unfortunately I'm 100 >>> miles away and he wouldn't have a clue how to compile and patch Wine. >>> I might have a stab at packaging a custom version :) >>> >>> Luke. >>> >>> >> Thank you all for your messages, I'm glad it's useful for somebody :-) >> I was thinking too on packaging a custom version with the patches on >> my tree.... btw, I have a couple more which weren't applied because >> "ugly", one allows printing on formats different than printer's >> default one (a need for most autocad users...). >> I'm not too good on debian packaging, but if you have some script >> that can do it we could find a place to host them. >> >> Ciao >> >> Max >> >> >> >> >> > > I have a place we could host the packages, but it would take me some > time to learn how to package Wine... I've only ever done small > libraries. > > Scott, are you the Ubuntu maintainer? If so, do you have some script > for building the packages? > > Luke. > > > Well, I do have some script to package an app (Ultimate++), I could adapt them to package wine. Next days maybe..... Max

May 1, 2009

Re: Added Polish translation

by Jeremy Newman

Issues with your website translation files: * please strip the html,head,meta, and body HTML tags from the templates. The are not needed as they are generated by the website. * your editor is munging the template vars like {$root} to %7B$root%7D * your editor is adding LANG="pl-PL" to many tags, it is not needed as the files are UTF-8, and the website engine, sets the correct headers. It would be better if you used a plain text editor rather than open office to edit the files. -Newman Łukasz Wojniłowicz wrote: > From: Łukasz Wojniłowicz <Wojnilowicz(a)nslw.hstl.put.poznan.pl> > > --- > include/data.php | 4 + > templates/pl/.cvsignore | 2 + > templates/pl/announce.template | 19 +++ > templates/pl/download.template | 280 ++++++++++++++++++++++++++++++++++++ > templates/pl/download/deb.template | 127 ++++++++++++++++ > templates/pl/home.template | 70 +++++++++ > templates/pl/interview.template | 18 +++ > templates/pl/irc.template | 27 ++++ > templates/pl/lang.template | 36 +++++ > templates/pl/news.template | 21 +++ > templates/pl/search.template | 40 +++++ > 11 files changed, 644 insertions(+), 0 deletions(-) > create mode 100644 templates/pl/.cvsignore > create mode 100644 templates/pl/announce.template > create mode 100644 templates/pl/download.template > create mode 100644 templates/pl/download/deb.template > create mode 100644 templates/pl/home.template > create mode 100644 templates/pl/interview.template > create mode 100644 templates/pl/irc.template > create mode 100644 templates/pl/lang.template > create mode 100644 templates/pl/news.template > create mode 100644 templates/pl/search.template > > diff --git a/include/data.php b/include/data.php > index a0e2f5f..c9a656b 100644 > --- a/include/data.php > +++ b/include/data.php > @@ -61,6 +61,10 @@ class data > 'name' => 'Français', > 'change' => 'Changez la langue' > ), > + 'pl' => array( > + 'name' => 'Polski', > + 'change' => 'Zmień język' > + ), > 'pt' => array( > 'name' => 'Português', > 'change' => 'Mudar a língua' > diff --git a/templates/pl/.cvsignore b/templates/pl/.cvsignore > new file mode 100644 > index 0000000..0ba44f6 > --- /dev/null > +++ b/templates/pl/.cvsignore > @@ -0,0 +1,2 @@ > +docs > +winapi_stats.template > diff --git a/templates/pl/announce.template b/templates/pl/announce.template > new file mode 100644 > index 0000000..2181953 > --- /dev/null > +++ b/templates/pl/announce.template > @@ -0,0 +1,19 @@ > +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > +<HTML> > +<HEAD> > + <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> > + <TITLE></TITLE> > + <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0 (Linux)"> > + <META NAME="CREATED" CONTENT="0;0"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGED" CONTENT="20090429;16395900"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > +  > +  > +</HEAD> > +<BODY LANG="en-US" DIR="LTR"> > +<H1 LANG="pl-PL">Ogłoszenie nowego Wine</H1> > + > + > +</BODY> > +</HTML> > \ No newline at end of file > diff --git a/templates/pl/download.template b/templates/pl/download.template > new file mode 100644 > index 0000000..be85e37 > --- /dev/null > +++ b/templates/pl/download.template > @@ -0,0 +1,280 @@ > +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > +<HTML> > +<HEAD> > + <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> > + <TITLE></TITLE> > + <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0 (Linux)"> > + <META NAME="CREATED" CONTENT="0;0"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGED" CONTENT="20090429;17143300"> > + <META NAME="Info 1" CONTENT=""> > + <META NAME="Info 2" CONTENT=""> > + <META NAME="Info 3" CONTENT=""> > + <META NAME="Info 4" CONTENT=""> > +  > +  > +</HEAD> > +<BODY LANG="en-US" DIR="LTR"> > +<H1 LANG="pl-PL">Pobieralnia Wine</H1> > +<H2 LANG="pl-PL" STYLE="margin-top: 0cm; margin-bottom: 0.26cm">Wine > +ze wsparciem technicznym</H2> > +<TABLE BORDER=0 CELLPADDING=5 CELLSPACING=1 BGCOLOR="#efefef"> > + <TR> > + <TD BGCOLOR="#000000"> > + Produkt > + </TD> > + <TD BGCOLOR="#000000"> > + Opis > + </TD> > + </TR> > + <TR> > + <TD BGCOLOR="#ffffff"> > + <A HREF="http://www.codeweavers.com/products/download_trial/"><IMG SRC="%7B$root%7D/images/distro/crossover.png" NAME="graphics1" ALT="CrossOver Linux or Mac" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A><A HREF="http://www.codeweavers.com/products/download_trial/"> > + </A> > + > + </TD> > + <TD BGCOLOR="#ffffff"> > + <A HREF="http://www.codeweavers.com/products/">CrossOver</A> > + jest dobrze wykończoną wersją dostarczaną przez <A HREF="http://www.codeweavers.com/">CodeWeavers</A>. > + CrossOver usprawnia używanie Wine, a CodeWeavers zapewnia > + wspaniałe wsparcie techniczne swoim użytkownikom. Wszystkie > + fundusze ze sprzedaży CrossOvera są przekazywane bezpośrednio > + jako wsparcie dla programistów pracujących nad Wine. Tak więc > + CrossOver jest jest wspaniałą drogą uzyskania wsparcia jak > + również wspierania Projektu Wine. CodeWeavers dostarcza w pełni > + funkcjonalną <A HREF="http://www.codeweavers.com/products/download_trial/">wersję > + trialową CrossOver</A>. > + > + </TD> > + </TR> > +</TABLE> > +To poparcie jest głównym dowodem > +uznania wymaganym przez CodeWeavers w zamian za hostowanie strony > +Wine. > +<H2 LANG="pl-PL" STYLE="margin-top: 0cm; margin-bottom: 0.13cm"><A NAME="binary"></A> > +Pobieralnia binariów Wine</H2> > +<TABLE WIDTH=100% CELLPADDING=2 CELLSPACING=2> > + <TR> > + <TD WIDTH=200> > + Najnowsze stabilne wydanie: > + </TD> > + <TD> > + Wine {$config_stable_release} > + </TD> > + <TD ROWSPAN=2 VALIGN=TOP> > + Zajrzyj > + do <A HREF="http://wiki.winehq.org/HowTo">samouczka konfiguracji i > + instalacji</A>, aby zaznajomić się z czynnościami > + po-instalacyjnymi. > + </TD> > + </TR> > + <TR> > + <TD> > + Najnowsze rozwojowe wydanie: > + </TD> > + <TD> > + Wine {$config_master_release} > + </TD> > + </TR> > +</TABLE> > +<TABLE BORDER=0 CELLPADDING=5 CELLSPACING=1 BGCOLOR="#efefef"> > + <TR> > + <TD BGCOLOR="#000000"> > + System > + </TD> > + <TD BGCOLOR="#000000"> > + Notki > + </TD> > + <TD BGCOLOR="#000000"> > + Opiekun > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="%7B$root%7D/download/deb"><IMG SRC="%7B$root%7D/images/distro/ubuntu.png" NAME="graphics2" ALT="Ubuntu linux" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A> > + > + </TD> > + <TD> > + <A HREF="%7B$root%7D/download/deb">Ubuntu</A> > + binare i źródłowe paczki .deb dla Ubuntu Hardy (8.04), Intrepid > + (8.10), i Jaunty (9.04) > + > + </TD> > + <TD> > + <A HREF="mailto:scott(a)open-vote.org">Scott > + Ritchie</A> > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="%7B$root%7D/download/deblenny"><IMG SRC="%7B$root%7D/images/distro/debian.png" NAME="graphics3" ALT="Debian Linux" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A> > + > + </TD> > + <TD> > + <A HREF="%7B$root%7D/download/deblenny">Debian</A> > + binarne paczki .deb dla Debian Lenny, Squeeze i Sid > + </TD> > + <TD> > + <A HREF="mailto:repository(a)lamaresh.net">Maurilio > + Genovese</A> <A HREF="mailto:ben.klein(a)lamaresh.net">Ben Klein</A> > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="http://fedoraproject.org/wiki/AndreasBierfert/Wine"><IMG SRC="%7B$root%7D/images/distro/redhat.png" NAME="graphics4" ALT="RedHat Linux" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A> > + > + </TD> > + <TD> > + <A HREF="http://fedoraproject.org/wiki/AndreasBierfert/Wine">Red > + Hat / CentOS / Fedora</A> binarne i > + źródłowe .rpmy dla Red Hat Enterprise Linux 4, 5; CentOS 4, 5; > + Fedora Core 5, 6; Fedora Linux 7 i kompatybilnych dystrybucji. The > + wine meta package is available via <TT>yum</TT> > + through the EPEL / Fedora Extras / Fedora repository by running <TT>$ > + yum install wine </TT>" > + > + </TD> > + <TD> > + <A HREF="mailto:andreas.bierfert_at_lowlatency.de">Andreas > + Bierfert</A> > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="http://en.opensuse.org/Wine#Repositories"><IMG SRC="%7B$root%7D/images/distro/suse.png" NAME="graphics5" ALT="SUSE Linux" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A> > + > + </TD> > + <TD> > + <A HREF="http://en.opensuse.org/Wine#Repositories">SUSE</A> > + binarne i źródłowe .rpmy i dzienne zrzuty RPM dla openSUSE > + 10.3, 11.0, 11.1 i SLES 9 i SLE 10. Starsze wersje paczek dostępne > + na <A HREF="http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=7…">SourceForge</A> > + > + > + </TD> > + <TD> > + <A HREF="mailto:meissner(a)suse.de">Marcus > + Meissner</A> > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=8…"><IMG SRC="%7B$root%7D/images/distro/mandriva.png" NAME="graphics6" ALT="Mandriva Linux" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A> > + > + </TD> > + <TD> > + <A HREF="http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=8…">Mandriva</A> > + binarne .rpmy dla Mandriva Linux 2006, 2007, i 2008. Pobierz > + paczkę 2008.1 jeżeli twoja Mandriva to wydanie 2008.1 , np. 2008 > + Spring. Pobierz paczkę 2008.0 jeżeli twoja Mandriva jest > + pierwszym wydaniem z 2008 roku. > + </TD> > + <TD> > + <A HREF="mailto:marco(a)mandrivaclub.nl">Marco > + Meijer</A> > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=6…"><IMG SRC="%7B$root%7D/images/distro/slackware.png" NAME="graphics7" ALT="Slackware linux" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A> > + > + </TD> > + <TD> > + <A HREF="http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=6…">Slackware</A> > + binarne .tgz dla Slackware 10.2 > + </TD> > + <TD> > + <A HREF="mailto:sadam(a)clemson.edu">Adam > + Schreiber</A> > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="http://www.freshports.org/emulators/wine/"><IMG SRC="%7B$root%7D/images/distro/freebsd.png" NAME="graphics8" ALT="FreeBSD" ALIGN=BOTTOM WIDTH=50 HEIGHT=54 BORDER=0></A> > + > + </TD> > + <TD> > + <A HREF="http://www.freshports.org/emulators/wine/">FreeBSD</A> > + źródła dla FreeBSD 5.3 i późniejszych > + </TD> > + <TD> > + <A HREF="mailto:gerald(a)pfeifer.com">Gerald > + Pfeifer</A> > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="http://www.pbidir.com/bt/search/?str=wine&search=Search"><IMG SRC="%7B$root%7D/images/distro/pcbsd.png" NAME="graphics9" ALT="FreeBSD" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A> > + > + </TD> > + <TD> > + <A HREF="http://www.pbidir.com/bt/search/?str=wine&search=Search">PC-BSD</A> > + binarne paczki .pbi dla PC-BSD (system bazujący na FreeBSD) > + </TD> > + <TD> > + <A HREF="mailto:kris(a)pcbsd.com">Kris Moore</A> > + </TD> > + </TR> > +</TABLE> > +<H2 LANG="pl-PL" STYLE="margin-top: 0cm; margin-bottom: 0.26cm">Aplikacje > +osób trzecich</H2> > +Czasami pewne modyfikacje Wine mogą sprawić, > +że aplikacja będzie działać, ale z pewnych powodów zmiany te nie > +mogą być wcielone do Wine. Stworzono różne aplikacje (tzw. > +aplikacje osób trzecich), aby pomóc przezwyciężyć niedobory w > +Wine. Aplikacje te są całkowicie niewspierane przez programistów > +Wine, jednakże mogą ci się przydać. Aby dowiedzieć się więcej, > +odwiedź <A HREF="http://wiki.winehq.org/ThirdPartyApplications">naszą > +stronę wiki</A> w poszukiwaniu aplikacji osób trzecich. > +<H2 LANG="pl-PL">Pobieralnia źródeł Wine</H2> > +<TABLE BORDER=0 CELLPADDING=5 CELLSPACING=1 BGCOLOR="#efefef"> > + <TR> > + <TD BGCOLOR="#000000"> > + Położenie > + </TD> > + <TD BGCOLOR="#000000"> > + Opis > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=7…" TARGET="_blank">sourceforge.net</A> > + </TD> > + <TD> > + Nasza oficjalna strona źródeł. > + > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="http://wiki.winehq.org/GitWine">source.winehq.org/git</A> > + > + > + </TD> > + <TD> > + Do najnowszych wydań rozwojowych. > + > + </TD> > + </TR> > + <TR BGCOLOR="#ffffff"> > + <TD> > + <A HREF="http://ibiblio.org/pub/linux/system/emulators/wine/">ibiblio.org</A> > + </TD> > + <TD> > + Alternatywna strona z oficjalnymi źródłami i > + dokumentacją. > + > + </TD> > + </TR> > +</TABLE> > + > +Notka: > +Zobacz <A HREF="http://wiki.winehq.org/Recommended_Packages">zalecane > +paczki</A> aby uzyskać pomoc przy konfiguracji i kompilacji Wine. > +<H2 LANG="pl-PL"><A NAME="link2us"></A>Link do nas</H2> > +<A HREF="http://www.winehq.org/download" TARGET="_blank"><IMG SRC="%7B$root%7D/images/download_wine.png" NAME="graphics10" ALT="Download Wine" ALIGN=LEFT HSPACE=5 WIDTH=88 HEIGHT=31 BORDER=1></A>Użyj > +tego obrazka jeżeli chcesz utworzyć dowiązanie do naszej > +pobieralni. > + > +</BODY> > +</HTML> > \ No newline at end of file > diff --git a/templates/pl/download/deb.template b/templates/pl/download/deb.template > new file mode 100644 > index 0000000..fc532fe > --- /dev/null > +++ b/templates/pl/download/deb.template > @@ -0,0 +1,127 @@ > +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > +<HTML> > +<HEAD> > + <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> > + <TITLE></TITLE> > + <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0 (Linux)"> > + <META NAME="CREATED" CONTENT="0;0"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGED" CONTENT="20090429;15595600"> > + <META NAME="Info 1" CONTENT=""> > + <META NAME="Info 2" CONTENT=""> > + <META NAME="Info 3" CONTENT=""> > + <META NAME="Info 4" CONTENT=""> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > +  > +  > +</HEAD> > +<BODY LANG="en-US" DIR="LTR"> > +<H1><A HREF="http://www.ubuntu.com/" TARGET="_new"><IMG SRC="%7B$root%7D/images/distro/ubuntu.png" NAME="graphics1" ALT="Ubuntu Logo" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A> > +Wine dla Ubuntu i pochodnych Ubuntu > +<A HREF="http://www.debian.org/" TARGET="_new"><IMG SRC="%7B$root%7D/images/distro/ubuntu.png" NAME="graphics2" ALT="Ubuntu Logo" ALIGN=BOTTOM WIDTH=50 HEIGHT=50 BORDER=0></A></H1> > +Ubuntu i inne dystrybucje bazujące na Debianie > +używają specjalnego narzędzia zwanego APT do zarządzania > +paczkami. APT jest zdolne automagicznie zainstalować wszystkie > +potrzebne zależności dla paczki z programem, jak również > +utrzymywać zawsze najnowszą wersję paczki, poprzez przeszukiwanie > +czegoś, co jest znane pod nazwą repozytoria APT. Ubuntu ma swoje > +własne repozytorium programów, które zawiera w sobie Wine, > +jednakże my utrzymujemy nasze własne repozytorium najnowszych > +dostępnych paczek beta, które można tutaj pobrać. > +<H2 LANG="pl-PL">Uwaga: To są paczki beta</H2> > +Te paczki są paczkami beta. Oznacza to, że > +okresowo mogą cierpieć z powodu <A HREF="http://wiki.winehq.org/Regression">regresji</A>, > +a aktualizacja do nich może popsuć funkcjonalność Wine. Jeżeli w > +twoim przypadku ostatnie stabilne wydanie Wine (aktualnie Wine 1.0.1) > +działa, to nie musisz używać paczek beta. > +<H2 LANG="pl-PL">Dodawanie repozytorium APT WineHQ:</H2> > +Otwórz Źródła oprogramowania z menu > +System->Administracja->Źródła oprogramowania. > +Następnie przejdź na zakładkę Oprogramowanie osób trzecich > +i kliknij Dodaj... > +<IMG SRC="%7B$root%7D/images/distro/ubuntu-softwaresources1.png" NAME="graphics3" ALT="System->Administration->Software Sources->Third Party Software" ALIGN=BOTTOM WIDTH=531 HEIGHT=509 BORDER=0> > + > +Następnie, wklej jedną z poniższych linijek > +zależnie od wersji twojego systemu. > +Dla Ubuntu Jaunty (9.04): deb > +http://wine.budgetdedicated.com/apt jaunty main #WineHQ - Ubuntu 9.04 > +"Jaunty Jackalope" > +Dla Ubuntu Intrepid (8.10): deb > +http://wine.budgetdedicated.com/apt intrepid main #WineHQ - Ubuntu > +8.10 "Intrepid Ibex" > +Dla Ubuntu Hardy (8.04): deb > +http://wine.budgetdedicated.com/apt hardy main #WineHQ - Ubuntu 8.04 > +"Hardy Heron" > +<H2 LANG="pl-PL">Przyznanie zaufania repozytorium APT WineHQ i > +instalowanie Wine:</H2> > +Po dodaniu repozytorium, potrzebujesz również dodać > +klucz do tego repozytorium do twojej systemowej listy zaufanych > +kluczy. > +<A HREF="http://wine.budgetdedicated.com/apt/Scott%20Ritchie.gpg">Pobierz > +i zapisz klucz Scotta Ritchiego</A> (prawy > +przycisk myszy -> zapisz jako) na pulpicie. Następnie przejdź na > +zakładkę Uwierzytelnianie, > +kliknij Zaimportuj plik klucza... , > +i wybierz plik klucza, którego właśnie zapisałeś (Scott > +Ritchie.gpg). Możesz usunąć ten plik > +po wykonaniu tego kroku. > +<IMG SRC="%7B$root%7D/images/distro/ubuntu-softwaresources2.png" NAME="graphics4" ALT="System->Administration->Software Sources->Authentication" ALIGN=BOTTOM WIDTH=531 HEIGHT=509 BORDER=0> > + > +Kliknij zamknij, aby zakończyć, a potem > +uaktualnij dane o paczkach w > +momencie pytania. Jeżeli masz zainstalowane Wine to systemowy > +menadżer aktualizacji poinformuje cię o najnowszym wydaniu Wine > +beta i zapyta cię o aktualizację. Jeżeli nie instalowałeś > +jeszcze Wine, to przejdź do Aplikacje->Dodaj/usuń > +aplikacje > +i poszukaj Wine lub po prostu <A HREF="apt://wine">kliknij na tego > +linka</A>. > +<H2 LANG="pl-PL">Aktualizacja do nowej wersji Ubuntu</H2> > +Jeżeli aktualizujesz cały system np. przechodzisz z > +Ubuntu 8.10 na 9.04, to będzie konieczny powrót do tej strony i > +dodanie repozytorium do nowej wersji systemu. Wbudowany menadżer > +aktualizacji nie zmieni automatycznie repozytorium Wine. > +<H2 LANG="pl-PL">Starsze paczki .deb</H2> > +Jako że repozytorium APT może przechowywać > +jedynie najnowsze paczki, tak więc starsze wersje paczek są > +dostępne w <A HREF="http://wine.budgetdedicated.com/archive/index.html">archiwum > +WineHQ paczek .deb</A>. > +Możesz zainstalować pobrane paczki klikając na nie > +dwukrotnie. > +<H2 LANG="pl-PL">Alternatywne komendy wiersza poleceń do > +zainstalowania Wine:</H2> > +Możliwe jest także dodanie repozytoriów Wine i > +zainstalowanie go z wiersza poleceń. Jest to użyteczne w przypadku > +Kubuntu, Xubuntu, i innych pochodnych Ubuntu. > +Najpierw otwórz okno terminalu > +(Aplikacje->Akcesoria->Terminal). Następnie dodaj klucz > +repozytorium do systemowej listy zaufanych kluczy APT przez wklejenie > +następującej linijki do twojego terminalu: > +wget -q > +http://wine.budgetdedicated.com/apt/387EE263.gpg -O- | sudo apt-key > +add - > +Następnie, dodaj repozytorium do systemowej listy > +źródeł APT: > +Dla Ubuntu Jaunty (9.04): sudo wget > +http://wine.budgetdedicated.com/apt/sources.list.d/jaunty.list -O > +/etc/apt/sources.list.d/winehq.list > +Dla Ubuntu Intrepid (8.10): sudo wget > +http://wine.budgetdedicated.com/apt/sources.list.d/intrepid.list -O > +/etc/apt/sources.list.d/winehq.list > +Dla Ubuntu Hardy (8.04): sudo wget > +http://wine.budgetdedicated.com/apt/sources.list.d/hardy.list -O > +/etc/apt/sources.list.d/winehq.list > +Następnie zaktualizuj informacje o paczkach APT > +wpisując 'sudo apt-get update'. Teraz możesz zainstalować > +Wine zwyczajnie lub wpisując 'sudo apt-get install wine' w > +terminalu. > + > + > +Bardzo szybki i niezawodny webhosting dla > +repozytoriów APT jest łaskawie dostarczany przez > +<A HREF="http://www.budgetdedicated.com/">budgetdedicated.com</A>. > +</BODY> > +</HTML> > \ No newline at end of file > diff --git a/templates/pl/home.template b/templates/pl/home.template > new file mode 100644 > index 0000000..bd88eba > --- /dev/null > +++ b/templates/pl/home.template > @@ -0,0 +1,70 @@ > +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > +<HTML> > +<HEAD> > + <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> > + <TITLE></TITLE> > + <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0 (Linux)"> > + <META NAME="CREATED" CONTENT="0;0"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGED" CONTENT="20090429;15261400"> > +  > +  > +  > +</HEAD> > +<BODY LANG="en-US" DIR="LTR"> > +<FORM NAME="donateForm" ACTION="https://www.paypal.com/cgi-bin/webscr" METHOD="POST"> > + <INPUT TYPE=HIDDEN NAME="cmd" VALUE="_xclick"> > + <INPUT TYPE=HIDDEN NAME="business" VALUE="donate(a)winehq.org"> > + <INPUT TYPE=HIDDEN NAME="item_name" VALUE="Wine donation"> > +</FORM> > +<DIV ID="main_left" DIR="LTR"> > + <UL> > + <LI><A HREF="%7B$root%7D/about/">Informacje</A> > + > + Przegląd funkcji Wine. > + <LI><A HREF="%7B$root%7D/download/">Pobieralnia</A> > + > + Ściągnij Wine teraz! > + <LI><A HREF="%7B$root%7D/help/">Pomoc!</A> > + > + Dokumentacja, Wsparcie, i Wiki. > + <LI><A HREF="%7B$root%7D/devel/">Rozwój</A> > + > + Źródła Wine, Szukanie Robaków, itp. > + <LI><A HREF="javascript:document.donateForm.submit();">Darowizny</A> > + Ofiary dla Wine. > + </UL> > +</DIV> > +<DIV ID="main_right" DIR="LTR"> > + <H3 LANG="pl-PL" STYLE="border: none; padding: 0cm">Najnowsze > + wydania</H3> > + <TABLE CELLPADDING=2 CELLSPACING=2> > + <TR> > + <TD> > + Stabilne: > + </TD> > + <TD> > + <A HREF="%7B$root%7D/announce/%7B$config_stable_release%7D">Wine {$config_stable_release}</A> > + (<A HREF="http://source.winehq.org/git/wine.git?a=shortlog;h=refs/tags/wine-%7B$confi…">zmiany</A>) > + > + > + </TD> > + </TR> > + <TR> > + <TD> > + Rozwojowe: > + </TD> > + <TD> > + <A HREF="%7B$root%7D/announce/%7B$config_master_release%7D">Wine {$config_master_release}</A> > + (<A HREF="http://source.winehq.org/git/wine.git?a=shortlog;h=refs/tags/wine-%7B$confi…">zmiany</A>) > + > + > + </TD> > + </TR> > + </TABLE> > + <H3 STYLE="margin-top: 0.4cm; border: none; padding: 0cm"><A HREF="%7B$root%7D/news/">Aktualności</A></H3> > + <A HREF="%7B$root%7D/news/">więcej > + aktualności...</A> > +</DIV> > +</BODY> > +</HTML> > \ No newline at end of file > diff --git a/templates/pl/interview.template b/templates/pl/interview.template > new file mode 100644 > index 0000000..c0d6329 > --- /dev/null > +++ b/templates/pl/interview.template > @@ -0,0 +1,18 @@ > +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > +<HTML> > +<HEAD> > + <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> > + <TITLE></TITLE> > + <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0 (Linux)"> > + <META NAME="CREATED" CONTENT="0;0"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGED" CONTENT="20090429;16091900"> > +  > +  > +</HEAD> > +<BODY LANG="en-US" DIR="LTR"> > +<H1 LANG="pl-PL">Wywiady</H1> > + > + > +</BODY> > +</HTML> > \ No newline at end of file > diff --git a/templates/pl/irc.template b/templates/pl/irc.template > new file mode 100644 > index 0000000..53bbdd7 > --- /dev/null > +++ b/templates/pl/irc.template > @@ -0,0 +1,27 @@ > +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > +<HTML> > +<HEAD> > + <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> > + <TITLE></TITLE> > + <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0 (Linux)"> > + <META NAME="CREATED" CONTENT="0;0"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGED" CONTENT="20090429;16122300"> > +  > +  > +</HEAD> > +<BODY LANG="en-US" DIR="LTR"> > +<H1 LANG="pl-PL">Wsparcie na żywo</H1> > +<A HREF="http://www.freenode.net/">Freenode.net</A> > +hostuje kanał IRC dla Wine. Możesz wejść do pokoju rozmów > +używając programu IRC takiego jak np. <A HREF="http://www.xchat.org/">X-Chat</A>. > +Użyj ustawień wymienionych poniżej. > +<BLOCKQUOTE LANG="pl-PL">Serwer: irc.freenode.net Port: > +6667 Kanał: #winehq</BLOCKQUOTE> > +Jeżeli używasz Mozilli lub innej przeglądarki > +która wspiera uerele > +IRC, to możesz dołączyć do rozmowy klikając na > +<A HREF="irc://irc.freenode.net/#winehq">irc://irc.freenode.net/#winehq</A>. > +  > +</BODY> > +</HTML> > \ No newline at end of file > diff --git a/templates/pl/lang.template b/templates/pl/lang.template > new file mode 100644 > index 0000000..547a879 > --- /dev/null > +++ b/templates/pl/lang.template > @@ -0,0 +1,36 @@ > +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > +<HTML> > +<HEAD> > + <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> > + <TITLE></TITLE> > + <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0 (Linux)"> > + <META NAME="CREATED" CONTENT="0;0"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGED" CONTENT="20090429;16313700"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > +  > +  > +</HEAD> > +<BODY LANG="en-US" DIR="LTR"> > +<H1 LANG="pl-PL">{$langChange}</H1> > +Aktualny język: {$langCur} > +<UL> > + <LI><A HREF="%7B$root%7D/lang/en">English</A> > + (Angielski) > + <LI><A HREF="%7B$root%7D/lang/de">Deutsch</A> > + (Niemiecki) > + > + <LI><A HREF="%7B$root%7D/lang/es">EspaÃ±ol</A> > + (Hiszpański) > + > + <LI><A HREF="%7B$root%7D/lang/fr">FranÃ§ais</A> > + (Francuski) > + > + <LI><A HREF="%7B$root%7D/lang/pl">Polski</A> > + <LI><A HREF="%7B$root%7D/lang/pt">PortuguÃªs</A> > + (Portugalski) > + > +</UL> > +</BODY> > +</HTML> > \ No newline at end of file > diff --git a/templates/pl/news.template b/templates/pl/news.template > new file mode 100644 > index 0000000..4fc7ea0 > --- /dev/null > +++ b/templates/pl/news.template > @@ -0,0 +1,21 @@ > +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > +<HTML> > +<HEAD> > + <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> > + <TITLE></TITLE> > + <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0 (Linux)"> > + <META NAME="CREATED" CONTENT="0;0"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGED" CONTENT="20090429;16320300"> > +  > +  > +</HEAD> > +<BODY LANG="en-US" DIR="LTR"> > +<H1>Aktualności</H1> > +<UL> > + <LI><A HREF="%7B$root%7D/news/rss/">WineHQ News > + RSS Feed</A> > + > +</UL> > +</BODY> > +</HTML> > \ No newline at end of file > diff --git a/templates/pl/search.template b/templates/pl/search.template > new file mode 100644 > index 0000000..1c4a52a > --- /dev/null > +++ b/templates/pl/search.template > @@ -0,0 +1,40 @@ > +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > +<HTML> > +<HEAD> > + <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> > + <TITLE></TITLE> > + <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0 (Linux)"> > + <META NAME="CREATED" CONTENT="0;0"> > + <META NAME="CHANGEDBY" CONTENT="Łukasz Wojniłowicz"> > + <META NAME="CHANGED" CONTENT="20090429;16330800"> > +  > +  > +</HEAD> > +<BODY LANG="en-US" DIR="LTR"> > +<H1 LANG="pl-PL" STYLE="margin-top: 0cm; margin-bottom: 0.26cm">Wyniki > +wyszukiwania</H1> > +<DIV ID="cse-search-results" DIR="LTR"> > + > + > +</DIV> > +<SCRIPT> > + $.gglclientCoords = function() { > + var dimensions = {width: 0, height: 0}; > + if (document.documentElement) { > + dimensions.width = document.documentElement.offsetWidth; > + dimensions.height = document.documentElement.offsetHeight; > + } else if (window.innerWidth && window.innerHeight) { > + dimensions.width = window.innerWidth; > + dimensions.height = window.innerHeight; > + } > + return dimensions; > + } > + var googleSearchIframeName = "cse-search-results"; > + var googleSearchFormName = "cse-search-box"; > + var googleSearchFrameWidth = ($.gglclientCoords().width - 250); > + var googleSearchDomain = "www.google.com"; > + var googleSearchPath = "/cse"; > +</SCRIPT><SCRIPT SRC="http://www.google.com/afsonline/show_afs_search.js"></SCRIPT> > + > +</BODY> > +</HTML> > \ No newline at end of file

May 1, 2009

Re: ws2_32/tests: add initial tests for WSAStartup

by Alexandre Julliard

Austin English <austinenglish(a)gmail.com> writes: > CTESTS = \ > protocol.c \ > - sock.c > + sock.c \ > + startup.c There's no need to create a new file for such a small test. -- Alexandre Julliard julliard(a)winehq.org

May 1, 2009

Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more

by Susan Cragin

>I filed ubuntu bug 369762. Ubuntu didn't think much of my bug. They sent me the following recipe to cure it, and marked the bug invalid. 1) Edit /etc/pulse/client.conf, and change "autospawn = yes" to "autospawn = no" 2) `touch $HOME/.pulse_a11y_nostart' 3) `asoundconf list' 4) choose the desired card from the previous command's output, and use `asoundconf set-default-card CARD', replacing CARD as appropriate 5) `killall pulseaudio' https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/348353 mentions a recent kernel patch that routes all audio through pulse. I wonder if this patch is the culprit?

May 1, 2009

Re: Dib Engine: some update

by Luke Benstead

2009/5/1 Massimo Del Fedele <max(a)veneto.com>: > Luke Benstead ha scritto: >> >> 2009/5/1 Scott Ritchie <scott(a)open-vote.org>: >>> >>> Massimo Del Fedele wrote: >>>> >>>> I put on bug's 421 page an update of my dib engine. >>>> It implements AlphaBlend, StretchBlt and has many color fixes. >>>> If you want to try it, just follow instructions on above page. >>>> >>>> Ciao >>>> >>>> Max >>>> >>> Keep at it, it's very exciting :) >>> >>> Thanks, >>> Scott Ritchie >>> >>> >>> >> >> Yeah, nice work Max! You are doing an amazing job, I just wish that we >> knew how to get it into vanilla Wine! My bro really needs this to move >> his (and several work) machines to Ubuntu, but unfortunately I'm 100 >> miles away and he wouldn't have a clue how to compile and patch Wine. >> I might have a stab at packaging a custom version :) >> >> Luke. >> >> > Thank you all for your messages, I'm glad it's useful for somebody :-) > I was thinking too on packaging a custom version with the patches on > my tree.... btw, I have a couple more which weren't applied because > "ugly", one allows printing on formats different than printer's > default one (a need for most autocad users...). > I'm not too good on debian packaging, but if you have some script > that can do it we could find a place to host them. > > Ciao > > Max > > > > > I have a place we could host the packages, but it would take me some time to learn how to package Wine... I've only ever done small libraries. Scott, are you the Ubuntu maintainer? If so, do you have some script for building the packages? Luke.

May 1, 2009

Re: Trying buildbot on wine; foiled by distutils expecting mscoree to be resident?

by Louis Lenders

> so I tried doing > wine pywin32-212.win32-py2.6.exe > first. This fails immediately as described in > http://bugs.winehq.org/show_bug.cgi?id=13844 > It seems to terminate because it tries to get > a handle to the loaded copy of mscoree.dll > and fails (because there isn't one). > > The installer seems to have been created by python's distutils. > > Mark Hammond seems to be well aware of low level > issues that affect the installer, see e.g. > http://bugs.python.org/issue5075 > so perhaps he could explain why the installer expects > mscoree.dll to be resident... > > This is explained here: http://bugs.winehq.org/show_bug.cgi?id=6880#c7 (I guess it's the same issue) Copy and paste: --- snip --- I've seen quite some applications that fail in the end like this one: 0009:Call kernel32.GetModuleHandleA(011bf1d4 "mscoree.dll") ret=00c5936f 0009:Ret kernel32.GetModuleHandleA() retval=00000000 ret=00c5936f Then ExitProcess. --- snip --- This has nothing to do with this bug. The application uses dynamic msvc 7.1 runtime, which implicitly pulls mscoree.dll in. Normally mscrt __crtExitProcess() calls just ExitProcess() but on newer versions a call to __crtCorExitProcess() is made to ensure proper shutdown of managed parts (even if you don't use managed = .NET code). CorExitProcess() basically does this: --- snip --- hModule = GetModuleHandle("mscoree.dll"); if (hModule != NULL) { pfn = (PFN_EXIT_PROCESS) GetProcAddress( hModule, "CorExitProcess"); if (pfn != NULL) pfn(status); } --- snip --- If mscoree module or the export is not found it causes no harm. It works as designed. The reason for this additional (implicit) shutdown code is you have no control whether a part of operation system or application dll (3rd party/injected) might pull in managed stuff thats why this code exists. Regards

May 1, 2009

Re: Dib Engine: some update

by Massimo Del Fedele

Luke Benstead ha scritto: > 2009/5/1 Scott Ritchie <scott(a)open-vote.org>: >> Massimo Del Fedele wrote: >>> I put on bug's 421 page an update of my dib engine. >>> It implements AlphaBlend, StretchBlt and has many color fixes. >>> If you want to try it, just follow instructions on above page. >>> >>> Ciao >>> >>> Max >>> >> Keep at it, it's very exciting :) >> >> Thanks, >> Scott Ritchie >> >> >> > > Yeah, nice work Max! You are doing an amazing job, I just wish that we > knew how to get it into vanilla Wine! My bro really needs this to move > his (and several work) machines to Ubuntu, but unfortunately I'm 100 > miles away and he wouldn't have a clue how to compile and patch Wine. > I might have a stab at packaging a custom version :) > > Luke. > > Thank you all for your messages, I'm glad it's useful for somebody :-) I was thinking too on packaging a custom version with the patches on my tree.... btw, I have a couple more which weren't applied because "ugly", one allows printing on formats different than printer's default one (a need for most autocad users...). I'm not too good on debian packaging, but if you have some script that can do it we could find a place to host them. Ciao Max

May 1, 2009

Re: Dib Engine: some update

by Luke Benstead

2009/5/1 Scott Ritchie <scott(a)open-vote.org>: > Massimo Del Fedele wrote: >> >> I put on bug's 421 page an update of my dib engine. >> It implements AlphaBlend, StretchBlt and has many color fixes. >> If you want to try it, just follow instructions on above page. >> >> Ciao >> >> Max >> > > Keep at it, it's very exciting :) > > Thanks, > Scott Ritchie > > > Yeah, nice work Max! You are doing an amazing job, I just wish that we knew how to get it into vanilla Wine! My bro really needs this to move his (and several work) machines to Ubuntu, but unfortunately I'm 100 miles away and he wouldn't have a clue how to compile and patch Wine. I might have a stab at packaging a custom version :) Luke.

May 1, 2009

Re: [2/2] winex11.drv: export copied images as image/bmp

by Huw Davies

On Fri, May 01, 2009 at 01:25:33PM +0200, Alexandre Julliard wrote: > "Vincent Povirk" <vincent(a)codeweavers.com> writes: > > > + if (dibinfo->biBitCount < 16) > > + numcolors = dibinfo->biClrUsed || 1<<dibinfo->biBitCount; > > You have been doing too much Perl ;-) Hi Vincent, You may find bitmap_info_size() useful here. Huw.

May 1, 2009

Trying buildbot on wine; foiled by distutils expecting mscoree to be resident?

by Dan Kegel

I decided to try running buildbot on Wine today. The installation procedure is roughly wine msiexec /i python-2.6.2.msi /qb wine Twisted_NoDocs-8.2.0.win32-py2.6.exe The last bit complains Traceback (most recent call last): File "C:\Python26\scripts\twisted_postinstall.py", line 11, in <module> from twisted.scripts import tkunzip File "C:\Python26\lib\site-packages\twisted\scripts\tkunzip.py", line 26, in <module> from twisted.internet import reactor, defer File "C:\Python26\lib\site-packages\twisted\internet\reactor.py", line 37, in <module> from twisted.internet import selectreactor File "C:\Python26\lib\site-packages\twisted\internet\selectreactor.py", line 21, in <module> from twisted.internet import posixbase File "C:\Python26\lib\site-packages\twisted\internet\posixbase.py", line 25, in <module> from twisted.internet import tcp, udp File "C:\Python26\lib\site-packages\twisted\internet\tcp.py", line 78, in <module> from twisted.internet import defer, base, address File "C:\Python26\lib\site-packages\twisted\internet\defer.py", line 17, in <module> from twisted.python import log, failure, lockfile File "C:\Python26\lib\site-packages\twisted\python\lockfile.py", line 28, in <module> from win32api import OpenProcess ImportError: No module named win32api and hangs, possibly because of http://twistedmatrix.com/trac/ticket/3707 so I tried doing wine pywin32-212.win32-py2.6.exe first. This fails immediately as described in http://bugs.winehq.org/show_bug.cgi?id=13844 It seems to terminate because it tries to get a handle to the loaded copy of mscoree.dll and fails (because there isn't one). The installer seems to have been created by python's distutils. Mark Hammond seems to be well aware of low level issues that affect the installer, see e.g. http://bugs.python.org/issue5075 so perhaps he could explain why the installer expects mscoree.dll to be resident...

May 1, 2009

Re: [2/2] winex11.drv: export copied images as image/bmp

by Alexandre Julliard

"Vincent Povirk" <vincent(a)codeweavers.com> writes: > + if (dibinfo->biBitCount < 16) > + numcolors = dibinfo->biClrUsed || 1<<dibinfo->biBitCount; You have been doing too much Perl ;-) -- Alexandre Julliard julliard(a)winehq.org

May 1, 2009

Re: winemenubuilder: add Wine's MIME types to freedesktop (try2)

by Alexandre Julliard

Damjan Jovanovic <damjan.jov(a)gmail.com> writes: > +static void strlwrA(char *str) > +{ > + while ((*str = tolower(*str))) str++; > +} That won't work on utf-8. You should do it on the Unicode string before conversion. -- Alexandre Julliard julliard(a)winehq.org

May 1, 2009

Re: Dib Engine: some update

by Scott Ritchie

Massimo Del Fedele wrote: > I put on bug's 421 page an update of my dib engine. > It implements AlphaBlend, StretchBlt and has many color fixes. > If you want to try it, just follow instructions on above page. > > Ciao > > Max > Keep at it, it's very exciting :) Thanks, Scott Ritchie

May 1, 2009

Re: user32: combine horizontal and vertical window scroll bar info in a single structure.

by Alexandre Julliard

Rein Klazes <wijn(a)online.nl> writes: > - if (!infoPtr && alloc) > + if (!infoPtr && ( alloc || (wndPtr->dwStyle & (WS_VSCROLL | WS_HSCROLL)))) > { This bit doesn't look right, and defeats the purpose of the alloc flag. It would need some more test cases. -- Alexandre Julliard julliard(a)winehq.org

May 1, 2009

Re: tools/wine.desktop: reduce MIME types to application/x-ms-dos-executable and application/x-msi

by Scott Ritchie

Austin English wrote: > On Fri, May 1, 2009 at 3:05 AM, Damjan Jovanovic <damjan.jov(a)gmail.com> wrote: >> On Fri, May 1, 2009 at 12:31 AM, Scott Ritchie <scott(a)open-vote.org> wrote: >>> tools/wine.desktop: reduce MIME types to application/x-ms-dos-executable and >>> application/x-msi >>> >>> >>> >>> >> If you're not going to motivate this in the email, you could at least >> refer people to bug 18307. >> >> Also, do distributions outside Ubuntu come up with the same MIME types? >> >> Damjan >> >> >> > > What about .bat files, etc.? > Those already don't work as far as I know. An patch to shared-mime-info is needed for them. Thanks, Scott Ritchie

May 1, 2009

Re: tools/wine.desktop: reduce MIME types to application/x-ms-dos-executable and application/x-msi

by Scott Ritchie

Damjan Jovanovic wrote: > On Fri, May 1, 2009 at 12:31 AM, Scott Ritchie <scott(a)open-vote.org> wrote: >> tools/wine.desktop: reduce MIME types to application/x-ms-dos-executable and >> application/x-msi >> >> >> >> > > If you're not going to motivate this in the email, you could at least > refer people to bug 18307. > > Also, do distributions outside Ubuntu come up with the same MIME types? > > Damjan > > Fedora already patches out x-executable. Thanks, Scott Ritchie

May 1, 2009

Re: tools/wine.desktop: reduce MIME types to application/x-ms-dos-executable and application/x-msi

by Austin English

On Fri, May 1, 2009 at 3:05 AM, Damjan Jovanovic <damjan.jov(a)gmail.com> wrote: > On Fri, May 1, 2009 at 12:31 AM, Scott Ritchie <scott(a)open-vote.org> wrote: >> tools/wine.desktop: reduce MIME types to application/x-ms-dos-executable and >> application/x-msi >> >> >> >> > > If you're not going to motivate this in the email, you could at least > refer people to bug 18307. > > Also, do distributions outside Ubuntu come up with the same MIME types? > > Damjan > > > What about .bat files, etc.? -- -Austin

May 1, 2009

Re: Wine + Mono + application = library not found?

by Roderick Colenbrander

On Fri, May 1, 2009 at 1:36 AM, Seth Shelnutt <shelnutt2(a)gmail.com> wrote: > Hello all, > > I'm trying to see if I can get a folding monitor, > http://code.google.com/p/hfm-net/ working in Wine. I've installed the latest > wine, 1.1.20, and the latest mono for windows 2.4. It seems however that > either mono or Wine, I think wine, is not seeing the library file from gtk. > However it is in my lib folder. Does anyone have any idea where wine is > looking for the lib to be at? This is on a Debian "testing" (Squeeze I > guess, but I keep my repos under the "testing" and no name, I use the wine > "sid" repo) install. > > > shelnutt(a)K-Server:~/Downloads/HFM Release 0.1.1.10$ wine HFM.exe > > Unhandled Exception: System.TypeInitializationException: An exception was > thrown by the type initializer for System.Windows.Forms.MimeIconEngine ---> > System.DllNotFoundException: libgdk-x11-2.0.so.0 > at (wrapper managed-to-native) > System.Windows.Forms.GnomeUtil:gdk_init_check (intptr,intptr) > at System.Windows.Forms.GnomeUtil.Init () [0x00000] > at System.Windows.Forms.GnomeUtil.GetIcon (System.String icon, Int32 size) > [0x00000] > at System.Windows.Forms.GnomeHandler.AddGnomeIcon (System.String > internal_mime_type, System.String name) [0x00000] > at System.Windows.Forms.GnomeHandler.CreateUIIcons () [0x00000] > at System.Windows.Forms.GnomeHandler.Start () [0x00000] > at System.Windows.Forms.MimeIconEngine..cctor () [0x00000] > --- End of inner exception stack trace --- > at System.Windows.Forms.WinFileSystem..ctor () [0x00000] > at System.Windows.Forms.MWFVFS..ctor () [0x00000] > at System.Windows.Forms.FileDialog..ctor () [0x00000] > at System.Windows.Forms.OpenFileDialog..ctor () [0x00000] > at (wrapper remoting-invoke-with-check) > System.Windows.Forms.OpenFileDialog:.ctor () > at HFM.Forms.frmMain.InitializeComponent () [0x00000] > at HFM.Forms.frmMain..ctor () [0x00000] > at (wrapper remoting-invoke-with-check) HFM.Forms.frmMain:.ctor () > at HFM.Program.Main (System.String[] argv) [0x00000] > > shelnutt(a)K-Server:~/Downloads/HFM Release 0.1.1.10$ locate > libgdk-x11-2.0.so.0 > /home/shelnutt/opt/gps/lib/libgdk-x11-2.0.so.0 > /usr/lib/libgdk-x11-2.0.so.0 > /usr/lib/libgdk-x11-2.0.so.0.1600.1 > > > Thanks, > > Seth Shelnutt > > > > > When using win32 mono it should be using win32 gtk / gdk. I believe those dlls have about the same names as the linux ones. Make sure that win32 moni is really used. Second win32 mono only works for a limited number of apps for most things you need ms .net. I would suggest to try it using native mono first. Since the source is also around it would also be easy to locate mono bugs (hopefully the app doesn't make any win32 calls). Roderick

May 1, 2009

Re: tools/wine.desktop: reduce MIME types to application/x-ms-dos-executable and application/x-msi

by Damjan Jovanovic

On Fri, May 1, 2009 at 12:31 AM, Scott Ritchie <scott(a)open-vote.org> wrote: > tools/wine.desktop: reduce MIME types to application/x-ms-dos-executable and > application/x-msi > > > > If you're not going to motivate this in the email, you could at least refer people to bug 18307. Also, do distributions outside Ubuntu come up with the same MIME types? Damjan

May 1, 2009

error report

by Ruben Hillewaere

Hello, I wanted to install (Dar)wine on my Intel Mac, first I've tried with the binaries found on http://wiki.winehq.org/MacOSX/Installing The installation goes fine, but running any of the apps fails. So, instead, I've tried to build Wine from Scratch, this is what I get: ruben(a)CakeSlicer:~/distrib$ ./create_darwine_distrib.sh $VERSION ~/ Desktop/wine-$VERSION # Packaging Darwine for version 1.1.20 using Wine sources in /Users/ ruben/Desktop/wine-1.1.20... # Building Wine in /Users/ruben/Desktop/wine-1.1.20 (warning: takes a long time)... configure: WARNING: mach-o/dyld_images.h: present but cannot be compiled configure: WARNING: mach-o/dyld_images.h: check for missing prerequisite headers? configure: WARNING: mach-o/dyld_images.h: see the Autoconf documentation configure: WARNING: mach-o/dyld_images.h: section "Present But Cannot Be Compiled" configure: WARNING: mach-o/dyld_images.h: proceeding with the preprocessor's result configure: WARNING: mach-o/dyld_images.h: in the future, the compiler will take precedence configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to wine-devel(a)winehq.org ## configure: WARNING: ## ------------------------------------ ## configure: error: FreeType development files not found. Fonts will not be built. Use the --without-freetype option if you really want this. ***** Error: Can't build wine thanks for keeping me informed about this error, Ruben Hillewaere PhD student, COMO Vrije Universiteit Brussel Department of Computer Science Pleinlaan 2 B-1050 Brussels Belgium

May 1, 2009

Re: IE and MSN Messenger 7.0

by Remco

2009/4/27 Cissyvonwinckelmann <cissyvonwinckelmann(a)planet.nl>: > dag, > bestaat er voor mij nog een mogelijkheid om messenger 7.0 te downloaden. > Heb dus nog Windows Me, > heel graag antwoord, > groet cissy Cissy, je zit bij deze mailinglist verkeerd. Het onderwerp hier is de ontwikkeling van een programma (genaamd Wine) waarmee je Windows-programma's kan draaien onder andere besturingssystemen zoals Linux, Solaris en FreeBSD. Jij bent op zoek naar een oude versie van een Windows-programma. Die kan hier vinden: http://www.oldversion.com/MSN-Messenger.html Remco

May 1, 2009

Re: IE and MSN Messenger 7.0

by Remco

On Fri, May 1, 2009 at 1:18 AM, Ben Klein <shacklein(a)gmail.com> wrote: > 2009/5/1 Cissyvonwinckelmann <cissyvonwinckelmann(a)planet.nl>: >> hartelijk dank Benm ja ik moet snel een andere pc hebben, want dit is een >> hele ouwe dan krijg je de moeilijkheden, >> groetjes cissy >> > > I have to use Google Language Tools to translate your text, so I > apologise if I misunderstand you. You did indeed misunderstand him. I'll translate his messages: ----- Hi, Is there a possibility to still download Messenger 7.0? You see, I am still running Windows ME. Waiting for your answer, Cheers, cissy ----- And his next email: ----- Thank you very much, Ben. Yeah, I must get another PC soon, because this is an old one and that causes problems. Cheers, cissy. ----- So I'm pretty sure he's on the wrong mailing list. Remco

May 1, 2009