I ask it consisely, but maybe the answers could be posted as a news item on WineHQ. It would be great for Wine to get some exposure on tech sites from time to time. That requires some actual news (new minor releases aren't front-page news after all). So, what's the status/news of DX10? DX in general? the Mac-port? Wine 1.0? What's the status of anything else that has been a major thing last year? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Tuesday 19 December 2006 00:27, Remco wrote:
I ask it consisely, but maybe the answers could be posted as a news item on WineHQ. It would be great for Wine to get some exposure on tech sites from time to time. That requires some actual news (new minor releases aren't front-page news after all).
Well, there was somebody offering to pick up on Wine Weekly News, wonder what happened to that. Also, I'd disagree that minor releases aren't front-page news. There's usually a significant change in features (and bugs) in every release. :)
So, what's the status/news of DX10? DX in general? the Mac-port? Wine 1.0? What's the status of anything else that has been a major thing last year?
I think the DX work is focusing on DX9 so far, and probably will stay like that for a while. Maybe some of the D3D people can fill in on the details. We're also working on getting DInput to be less broken, and someone in IRC seemed interested in DMusic, which could really need some love. We've ironed out almost all the bugs for running native DPlay, and I'm still working on figuring out that protocol. I expect this to take a while, though. As I don't own an Intel Mac, I can't tell you much about the Mac port. It should work ok in X, the quartz driver is still pretty stubbed out for all I know (correct me if I'm wrong). Wine 1.0 is due to be out in 6-18 months, as it's been the last 14 years. Actually, all kidding aside, we might see something in that direction once the D3D development stabilizes. How long that'll take, well... That's been my impression from reading the mailing list, people working on the single areas might know more specific things, so please correct me if this is all wrong. :) Cheers, Kai -- Kai Blin, <kai Dot blin At gmail Dot com> WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin/ -- Will code for cotton.
The next issue of WWN is around half done and will most likely be submitted for the end of this week. It will focus on the major changes since the last issue and the work being done in d3dx. The problem has mainly been the size of wine and how many people there are working on it. Catching up on threads of discussion and the like takes a lot of caching of the wine-devel list and tracking people down to ask questions to get a grasp of that area of development is tricky. Expect the rate at which I am able to send in an edition to increase drastically once the first one is out. Also more worrying is that I can't think of a good quip to put at the start of the news letter! Edward On 12/19/06, Kai Blin <kai.blin(a)gmail.com> wrote:
Well, there was somebody offering to pick up on Wine Weekly News, wonder what happened to that. Also, I'd disagree that minor releases aren't front-page news. There's usually a significant change in features (and bugs) in every release. :)
Cheers, Kai
On Tuesday 19 December 2006 08:11, Edward Savage wrote:
The next issue of WWN is around half done and will most likely be submitted for the end of this week.
Great, thanks for picking this up. I remember WWN being incredibly helpful when I got started with Wine.
Also more worrying is that I can't think of a good quip to put at the start of the news letter!
I guess this is a matter of practice. I'd suggest bugging Brian to let you in on the secret of witty remarks for Wine Weekly News (WRWWN). Cheers, Kai -- Kai Blin, <kai Dot blin At gmail Dot com> WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin/ -- Will code for cotton.
On 19 déc. 06, at 00:51, Kai Blin wrote:
On Tuesday 19 December 2006 00:27, Remco wrote:
So, what's the status/news of DX10? DX in general? the Mac-port? Wine 1.0? What's the status of anything else that has been a major thing last year?
As I don't own an Intel Mac, I can't tell you much about the Mac port. It should work ok in X, the quartz driver is still pretty stubbed out for all I know (correct me if I'm wrong).
Kay, you're right, the quartz driver is stubbed out, and will probably stay as is until the graphics drivers' factorization in user32 is completed, or sufficiently advanced :( The winex11 -> user move tends to be really tricky as we could break many things for x11 platforms with those modifications. We also need to do that in a way that is acceptable for Alexandre. Which means, I think, not to reproduce the past errors (like extensive inter-calls between user32 and x11drv) in the x11drv architecture, that Alexandre had been fixing during last x11drv rewrite. Pierre.
On 12/18/06, Remco <remco47(a)yahoo.com> wrote:
So, what's the status/news of DX10? DX in general?
See : http://wiki.winehq.org/DirectX-ToDo That ToDo is up to date as far as I know, DX10 = 0% completeness. If anyone is aware of something in need of change on the DX-ToDo please fix it or let me know and ill update the page. Happy Holidays Tom
Am Dienstag 19 Dezember 2006 07:53 schrieb Tom Wickline:
On 12/18/06, Remco <remco47(a)yahoo.com> wrote:
So, what's the status/news of DX10? DX in general?
See : http://wiki.winehq.org/DirectX-ToDo
That ToDo is up to date as far as I know, DX10 = 0% completeness.
If anyone is aware of something in need of change on the DX-ToDo please fix it or let me know and ill update the page. DirectX10 will be after Wine 1.0 I am afraid. Development outside the tree may start earlier, but last I knew AJ plans a feature freeze soon(aka when d3d is stable), adding d3d10 would delay that way to much. Right now I am rewriting the state management in wined3d, which is the last big thing I really want to get in before the freeze.
That said, we're doing some preparative work for d3d10, like namespace cleanups. We also know the d3d10 changes a bit, and when we're making a design decision we decide with d3d10 in mind. That said, if anyone wants to jump in, he can start working on Direct3D10 support today. The first things will be easy, like adding the headers and writing stub versions of the interfaces.
"Stefan Dösinger" <stefan(a)codeweavers.com> wrote in message news:200612191308.05608.stefan(a)codeweavers.com...
DirectX10 will be after Wine 1.0 I am afraid. Development outside the tree may start earlier, but last I knew AJ plans a feature freeze soon(aka when d3d is stable), adding d3d10 would delay that way to much. Right now I am rewriting the state management in wined3d, which is the last big thing I really want to get in before the freeze.
Just wondered if D3D in a child window is likely to be implemented before the freeze?? See bug: http://bugs.winehq.org/show_bug.cgi?id=3568 Mark
participants (7)
-
Edward Savage -
Kai Blin -
Mark Hatsell -
Pierre d'Herbemont -
Remco -
Stefan Dösinger -
Tom Wickline