All the news that fits, we print.
This is the 345 issue of the Wine Weekly News publication. Its main goal is to continue with Wine 1.0 progress report and mention some really cool things wine has done recently! It also serves to inform you of what's going on around Wine. Wine is an open source implementation of the Windows API on top of X and Unix. Think of it as a Windows compatibility layer. Wine does not require Microsoft Windows, as it is a completely alternative implementation consisting of 100% Microsoft-free code, but it can optionally use native system DLLs if they are available. You can find more info at www.winehq.org
|
This week, 535 posts consumed 790 K. There were 107 different contributors. 61 (57%) posted more than once. 67 (62%) posted last week too. The top 5 posters of the week were:
|
| News: new WineTricks, 1.0 status updates and more | Archive | |
|---|---|---|
|
Wine
Dan Kegel is continuing his diligence in keeping us up to date on Wine 1.0. 19 days to code freeze (!) Big news of the week is an apparant regression in one of the release criteria apps. Also, happily, two bugs I had pushed off to 1.2 got fixed anyway (demonstrating the honorary nature of the release manager position :-) Changes since last week:
Deferred earlier, but fixed anyway:
Deferred earlier, but patch that really fixes it submitted, so undeferred:
Deferred:
New: Winetricks updates
Misc.
WWN Changes
There are some WWN translations floating around, but I don't know their URLs. If you're maintaining a WWN translation, or would like to do so in the future please send me an email! (Link at the top of the page) Special thanks to John Klehm and Jeff Zaroyko for helping edit WWN Drafts. | ||
| iTunes support is making progress! | Archive | |
|---|---|---|
|
iTunes
Maarten Lankhorst has been hard at work adding support for iTunes and some of its more advanced features (non-iphone/itouch ipod syncing). He writes in: Hi all, I submitted the ipod patches to wine-patches. This won't add support for ipod touch or iphones. I expect that all patches will be merged soon. If anyone feels adventurous they can try it. With the amount of people interested in it I decided to post an update on the mailing list so that everyone who picked up on the earlier threads can find it.
Instructions: So far there seems to be some confusion, so for the sake of clarity: This won't add support for ipod touch or iphones.
Cheers, | ||
| Dan Kegel on LUG Radio! | Archive | |
|---|---|---|
|
LUG Radio
Dan Kegel is going to be talking on LUG radio. Our most recent experience with LUG was Alexandre Julliard's interview a few months back. You can find some material Dan wrote up for his talk here I'm going to be giving a Wine talk at LugRadio Live 2008, April 12-13, in San Francisco. My talk is Saturday at 2:30; see http://lugradio.org/live/USA2008/schedule In a mixup at my favorite coffeehouse today (Stir Crazy), I was accidentally overcaffeinated, and wrote my entire presentation in about one sitting. It's online at http://kegel.com/wine/lugradiolive2008/ The slides are pretty basic; I'll talk a lot around them. If anybody feels like reviewing the slides and giving feedback, I'd appreciate it. If anybody's planning on attending the event, let's get together for lunch or coffee or something. - Dan | ||
| Optimizing Wine at the Compiler Level | Archive | |
|---|---|---|
|
Optimization
Steven Edwards recently sent in an interesting post about his efforts to compile wine with compilers other than GCC for the sake of compiler-level optimizations: Hi, Given we are coming up close to the freeze, I think this may be a good time to look in to optimizations. I propose we spend some time trying different compilers and profiling Wine under different usage patterns to see what type of speedup we can get. I'm going to see if its possible to compile Wine with LLVM and I think it would be a good idea if someone with an ICC license gave it another shot. Also any gentoo users lurking, now would be a good time to go crazy with your compiler flags, run some benchmarks and file bug reports.
-- There were of course some interested responses, some more concerned about the stability of compiling with GCC before even thinking of optimizing using others, Scott Ritchie: I'd settle for someone telling me which GCC version to use. If you are doing optimization testing, please make sure to test that copy protection hasn't broken as well :)
Thanks, Steve responded that of course he would check for that, but at the moment wasn't even close to having anything working! After some more work he wrote in with the following:
I wasted a bit more time on this than I should have but I was able to
get the 32bit icc to work on my 64bit host to compile Wine with a few
hacks. I've documented the process on the wiki and submitted Wine test
results. If anyone else has time, please try icc on a 32bit host and
let me know if you get a crash when compiling oleaut32. Later when I
have more time I am going to run some benchmarks comparing a directx
game under wine compiled with gcc and icc.
| ||
| WineConf 2008 | Archive | |
|---|---|---|
|
WineConf
Jeremy White has begun the planning of this year's annual WineConf. He writes in: Hi Folks, I'd like to start the planning for WineConf 2008. My sense is that 3 years in Europe and 1 year in the US is a reasonable balance, so I feel it makes sense to try to have it over here this year. Further, I would like to host WineConf this year in St. Paul, Minnesota, for a variety of reasons. First, it's a lot easier for me to help plan if it's here. Second, it's nice for CodeWeavers; it means we can have everyone, not just the developers, all together. Having Mandi able to physically intimidate people is very helpful for us, after all *grin*. My thought was to do it in late September, early October, so that the weather would not be so extreme. I realize that veterans of our last Minnesota meeting will be disappointed at the lack of the Ice Palace, but we'll try to find a way to make it up to you. Also, I know the travel costs will be hard for many people, given current travel costs, so I'm hoping to contribute funds (and perhaps do some fund raising) to help cover travel costs for Wine contributors. At any rate, that's my idea. I'm willing to be swayed if people object violently, or if a clear consensus for an alternate emerges. Thoughts? Comments? Cheers, Jeremy Replies were mixed about a US based WineConf but overall the majority seems to be alright with Jeremy's proposal. I look forward to seeing you all there! | ||
| Versioning .wine directories | ||
|---|---|---|
|
There have been some issues with .wine directories brought up on the users list, causing a proposal to version the .wine directories to surface. Dan kegel: On the wine-users list, we're getting a lot of users who have old or even ancient .wine directories, and whose problems go away with a fresh .wine directory Perhaps we should have wineprefixcreate stamp the version of wine the .wine directory was created with, make wine-1.0 refuse to run with pre-1.0 .wine directories, and require that future versions of wine run properly with .wine directories created by any earlier stable release of wine. It wouldn't be hard, at least at first, and it might save a lot of support inquiries. What say? Austin English agrees and points to a bug where he mentioned this idea some time back:
http://bugs.winehq.org/show_bug.cgi?id=9959
Stefan Dösinger points out his own personal experience with .wine issues: In the past I've had more problems with wineprefixcreate trashing my registry than I had with outdated registry entries. Especially if you have Internet Explorer or the DirectX SDK or runtime installed running wineprefixcreate has bad side effects. Austin English thinks the problem is still solvable though. We could still store the version of wine last used and issue a (gui?) warning if it's old/outdated telling the user to either run wineprefixcreate, which may be bad in some cases, or to reinstall their apps. Alexandre Julliard writes in with an interesting perspective I think we should stop telling people to blow away their .wine, and have them run wineprefixcreate instead. Then if wineprefixcreate doesn't do the update correctly we need to figure out why and fix it. Once we are confident that it can do the update safely we can have it run automatically when it detects an upgrade. | ||
| Windows version of Firefox in Wine | Archive | |
|---|---|---|
|
Firefox in Wine
WWN doesn't usually quote the user's mailing list however there was a very interesting post from a user. I have not verified the claims present but that the user expressed them still makes it interesting: User rockinup1231 writes in (emphasis added): I installed Java 1.6 update 5 and Firefox. Firefox works "okay" , and some elements like Flash objects (videos on youtube and cartoons on AlbinoBlackSheep to name some examples) work a bit faster than they do on the native linux version of Firefox, so I wanted to try Java. The discussion veered off on a tangent for a while, and led to a quality post about testing random things in general about Wine: Like me. [Testing Windows Java and Firefox is] exactly the kind of think I like doing; it's a good test of wine. If it doesn't work, I file bugs. Like, oh, say http://bugs.winehq.org/show_bug.cgi?id=4860 Perhaps that's what the original poster was thinking. One can imagine a real scenario where this would be useful. A user who wants to use one web browser for everything, and is forced to use the windows version of firefox by some awful windows-specific plugin, might well want to install the Windows version of Java and expect it to work. - Dan Dan Kegel also, in a different thread, wrote some comments about getting firefox 3 beta 4 to work in Wine: tried Firefox 3 beta 4 just now, and there were a few bugs that stood out in the first few minutes:
12305 Firefox 3 beta 4 font problem: colon displayed as 0038
unicode glyph-missing glyph Youtube seemed slow and hangy on the first video I tried, http://www.youtube.com/watch?v=jwMj3PJDxuo although it was fine in native firefox at the same time; perhaps the Windows version of the flash plugin is less resistant to network errors -- or Wine doesn't support some network feature that only matters during bad internet weather. That same video was fine later, as was a different video http://www.youtube.com/watch?v=OGxdgNJ_lZM (both worth watching, btw). It also output quite a few messages like fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:font:ExtTextOutW flags ETO_NUMERICSLOCAL | ETO_NUMERICSLATIN | ETO_PDY unimplemented Firefox 3 rc1 will be out in May, and release will be in early June, according to http://blog.wired.com/monkeybites/2008/03/mozilla-final-v.html Given that a lot of people have in the past used windows Firefox in wine to run native plugins, maybe we should get firefox 3 working well. Probably only five or six main issues. - Dan | ||
| .NET support in wine | Archive | |
|---|---|---|
|
.NET support
There have been a number of posts recently about more and more stuff beginning to work with .NET. While not even .NET 1.0 is officially supported it seems that every day or two we hear about more .net (even partial) success stories. Even .NET 2.0 is beginning to shape up: It looks like 'winetricks dotnet20' and current wine is good enough that .net support isn't quite the limiting factor anymore! See http://bugs.winehq.org/show_bug.cgi?id=8499 http://bugs.winehq.org/show_bug.cgi?id=12457 http://bugs.winehq.org/show_bug.cgi?id=12458 for three sizeable apps that actually put up their GUIs, at least briefly. MySQL Workbench actually runs well enough to explore the GUI. | ||
| Weekly AppDB/BugZilla Status Changes | Archive | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
AppDB / BugZilla
*Disclaimer: These lists of changes are automatically generated by information entered into the AppDB. These results are subject to the opinions of the users submitting application reviews. The Wine community does not guarantee that even though an application may be upgraded to 'Gold' or 'Platinum' in this list, that you will have the same experience and would provide a similar rating.
Updates by App Maintainers
Updates by the Public
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
All Kernel Cousin issues and summaries are copyright their original authors, and distributed
under the terms of the
GNU General Public License,
version 2.0.
