Wine has had a provisional date set for it's 1.0 (initial feature freeze) release - 6th June 2008
http://wiki.winehq.org/WineReleasePlan
Printable View
Wine has had a provisional date set for it's 1.0 (initial feature freeze) release - 6th June 2008
http://wiki.winehq.org/WineReleasePlan
So is this release supposed to be more official or what? Any new features or just more stability and compatibility?
1.0, I believe (but documentation's a bit thin on the subject) means that all documented Windows API functions have been implemented within Wine
This means, if you have made a windows program
and it uses the "proper" Windows interfaces (not any undocumented "back-door" hooks into the kernel)
Wine will run it
For those who don't know
Wine is a complete reimplementation of the Windows API sub-systems, built on top of a different kernel (Eg. Linux, FreeBSD, Mac OS X, Solaris, etc.)
the X windowing system (as used by said kernels)
and OpenGL
Wine is not an emulator
It's a compatibility layer
in fact, Wine is an acronym, for just that
Wine Is Not an Emulator
Instead,
when a Windows program makes a call to any Windows system function, the call is understood by Wine, and translated to the equivalent native system call
What does this mean?Code:void Win32_draw_window_on_screen(args)
{
// some argument reshuffling takes place
// so it conforms with the equivalent
// Linux call
Linux_draw_window_on_screen(args);
}
Well, your *nix system understands, and can execute windows binaries as if the program was native to your platform with negligible performance cost.
Why am I making such a big thing about this?
Well, the fact that the Windows binary execution environment has been completely recreated within *nix systems could see a few interesting shifts in the Windows world
First, and probably the most obvious
the biggest barrier to OS migration will be lifted.
the good old,
"I'd love to dump Windows for another OS, but I need to run program x which is Windows only, so I can't"
Second, is the possibility of "back-ports" being made for previous editions of Windows
calls to DirectX 10 functions, for example, being mapped to the equivalent OpenGL functions means DirectX 10 games running on Linux (or mac, or whatever)
It also means, Wine running on XP (yes, you can run Wine on Windows) providing a DirectX 10 back-port (via OpenGL) to Windows XP
**
Note:
DX10 is not scheduled for the 1.0 release
1.0 deals with a feature complete kernel implementation and associated sub-systems, only
Possibly full DX9 will be in 1.0 (seeing as it's currently at 95% completion now)
but, full DX10 (currently at 0%) will be in a future release
So basically... much more likely to work with anything? That is pretty sweet. Does that mean it also will be QUICK in running things? For example, I can run (an older version of) iTunes now, but it is very, very slow. Will this improve?
possibly
but, again, I reiterate
publicly documented API interfaces
with something like Itunes, there may well be undocumented hooks into the kernel (DRM, and such)
Itunes 7.6 is currently rated "silver"
meaning some stuff works, some doesn't
http://appdb.winehq.org/objectManage...sion&iId=10543
(buying from the Itunes store, in particular, is not working)
slightly off-topic,
but give Amarok or Exaile a go
(I know for a fact Amarok can sync to all ipods, except the touch)
Rule of thumb, you're a lot better off running native apps, if available, than running Windows apps on Wine
If you don't use the Itunes store, and don't own a touch, you should be good to go with native Linux media players
but anyway....
Flash CS3 still has a garbage rating which makes me sad as thats the biggest thing holding me back to windows. They're working on it tho. It's pretty big (and will probably be carried through with photoshop CS3 which is relatively high priority) so when its done, that'll be awesome for me.
Everything else I do, is already pretty much supported in wine now which is awesome. So, I'll wait for that then jump the sinking windows ship <3.
50% of the time i'm on the computer, I'm fooling around with flash and AS3 =/
Yay!
Edit: Never mind, I thought this was something else.
Grod - Why?
Arby - Dual boot... (or use CS2 which is supposed to work with wine very well, and CS3 really doesn't have any new features anyways)
Ynot - I hate amarok. I really like the iTunes feel of having all my music on one list at one time, and amarok doesn't let you do that without being incredibly slow. It is kind of a pain in the ass. I use rhythmbox, which is very, very quick and lightweight. Also I recently switched to rockbox.
Because Grod is a Vista-Hocker.
or use a virtual machineQuote:
Originally Posted by wasup
Rockbox fucking rocks :DQuote:
Originally Posted by wasup
Constantly switching is annoying and I tend to have it open 24/7 even if I'm not working in it. Thus, I just go to windoze at boot-up. And theres no such thing as flash CS2. It's flash 8 which doesn't support AS3. Being a scripter, that means ALOT and if I were go back to 8, I wouldn't be able to touch any of the things I've I'm working on/have worked on in the last year.Quote:
Originally Posted by wasup
Arby,
quick google turned this up
http://wine-review.blogspot.com/2008...unning-in.html
Hey I have a WINE question and I'm too lazy to look it up:
Most windows software, as is distributed, comes with an installer and all that stuff. How does WINE handle that? Do you run setup.exe with wine, and it does the right things (installs it in some directory, etc.)? How does it handle things like registry keys? It's one thing to translate API calls, but some things go beyond just the API (though I guess registry access is really part of the API, so wine can maintain a registry of its own... or something)
That's pretty sweet. I'll have to put it on my Ubuntu box.
Hopefully it'll be out and well tested when it's time for a new computer. This PPC one is getting kind of old.
Yeah, it runs the setup.exe and installs into a directory.
Most of the windows are half-missing =PQuote:
Originally Posted by Ynot
I might take it on a virtual machine, the extra overhead (is is normally very big?) probably wouldn't be too much of a problem.
Otherwise, i'll wait for bronze or silver on CS3 =P
Somehow I get the feeling that Wine 1.0 isn't gonna happen for quite some time. That will be great when it does, though.
Slightly off topic, but am I the only one who runs Wine under Mac OS X? I know ninja9578 doesn't have access to an x86 Mac, but I can't be the only one in the known universe. There are more users of Mac OS X than of F/OSS OSes (not counting servers), yet you never hear about Mac users compiling Wine. It's a lot more convenient than dual-booting or using virtual machines.
Well, almost all big Windows programs have ports to the Mac (a lot of the bigs ones went the other way) so they run natively on the Mac. There are far less ports to Linux.
All of my friends parallel boot if they need a Windows program. I was going to do that with my next computer, until I found out that Wind ran on OSX :P
Wine 1.0-rc1 released
http://winehq.org/?announce=1.0-rc1
looking like it's on schedule
Looking forward to seeing it in the repos. I assume Hardy will pick it up automatically, and it won't be considered a completely separate version to manually install...
WoW is now rated platinum, hopefully anti-aliasing will work.
Well, Wine 1.0 is here
17th June 2008Quote:
The Wine team is proud to announce that Wine 1.0 is now available. This is the first stable release of Wine after 15 years of development and beta testing. Many thanks to everybody who helped us along that long road!
While compatibility is not perfect yet, thousands of applications have been reported to work very well. Check http://appdb.winehq.org to see the details for your favorite applications.
The source is available now. Binary packages are in the process of being built, and will appear soon at their respective download locations.
Both Wine 1.0 & Firefox 3.0 official releases
funny how things work out
Looks nice. I just set up my father's new computer yesterday, I should probably install Wine on it since he's switching from Windows and may want some of his old programs. :?
I've always found it best to move people onto native apps
99% of the time, the native linux apps will be better, integration-with-the-rest-of-the-system wise
(functionally, there's piss-all difference - an email client is an email client - once you get over any aesthetic differences it's just an app to read your email, and they're all pretty much the same)
also, it kind of diminishes the ease and sophistication of package management, if their core apps are win32 running under wine
wine for games and legacy apps only
but thats just my opinion / experience...