With WineConf 2017 going on, Wine [Official Site] founder Alexandre Julliard has given his keynote speech which covers a number of topics which I will summarise for you.
Here's what they're expecting for Wine 3.0:
- Direct3D 11
- Direct3D command stream
- Android driver
- Message-mode pipes
- Version bumped to Windows 7
Roadmap for the future:
- OpenGL Core contexts
- Android packaging
- Code freeze (expected soon)
- 3.0 release (end of year)
- Direct3D 12 / Vulkan
- Wayland driver (they've started working on it)
They're also approaching 4 million lines of code (for those that care about that sort of thing). Sounds like a lot, but it's a rather complicated project of course.
I think that pretty much sums up everything included. If you wish to watch it yourself, you can find the video below:
YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Direct Link
Direct Link
Sounds like Wine is going to have a rather bright future, which is good news for those of you not wanting to give up a few Windows games and applications while using Linux.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: iiariFor those of us unfamiliar with the background/backstory, can someone explain the difference between Wine and Wine-staging? Are they different projects?
The first line on wine-staging.com says enough:
"Wine Staging is the testing area of winehq.org. It contains bug fixes and features, which have not been integrated into the development branch yet."
0 Likes
Quoting: iiariFor those of us unfamiliar with the background/backstory, can someone explain the difference between Wine and Wine-staging? Are they different projects?
Although Wine Staging was voted to be an official repository, for staged patch sets, 2 years ago... It's still viewed with some skepticism by most core Wine Developers. This mainly centres around some dubious Q/A practices in Wine Staging, and one "rogue" committer.
But prior to 2 years ago you effectively weren't allowed to:
file bugs against Wine Staging at the WineHQ Bugzilla or submit test results for Wine Staging at WineHQ AppDB... For the past 2 years (and on-going) Wine users can state they use Wine Staging on Wine HQ ...
So Wine Staging is under the WineHQ Umbrella of projects... But has it's own website and Git repository.
None of the Wine Staging Developers were able to make it to Wineconf this year - due to outside commitments...
Last edited by bobbywya on 31 October 2017 at 10:47 am UTC
0 Likes
Quoting: Sir_DiealotThe wayland part is what I don't get at all. Is wayland this broken still?No, Wayland isn't broken. It seems to work just fine for many use cases, otherwise Fedora wouldn't have it as default, and Ubuntu wouldn't be planning on adopting it quite soon. Seems to run nicely on my phone as well.
That said, Wayland is quite a departure from X or other traditional windowing systems, and that trips developers up. Porting software over can be anything but straightforward, and Wine's requirements are not exactly common. I'm sure there's a lot of work still needed to cover every use case. Broken is the wrong word to use in any case.
0 Likes
Quoting: Sir_DiealotThe wayland part is what I don't get at all. Is wayland this broken still?
Wayland doesn't let one application manipulate windows of another, so Wine can't use the same method of mapping Windows abstractions into native DE windows and widgets, like it did with X11. What they can do, is to use virtual desktop on Wayland.
0 Likes
Patreon
PayPal
See more from me