Every once in a while a developer from another project asks 'What could I do in my project to help Wine?'.
We know there is stuff that could help us, some have been discussed on the mailing list long ago, but there's no good trace of it so that we are usually unable to really come with a good answer.
So I created a Wiki page to keep track of these features we would need from other projects to make Wine better. There are some *BIG* caveats though:
* The page is 'http://wiki.winehq.org/WineWishes'. It may be a terrible name so I'm open to other name suggestions.
* Currently it's only linked to from my home page so it's pretty much impossible to find. I'm not sure where to link to it though? Would it be ok to link to it from the FrontPage? From the TodoList maybe?
* This stuff is pretty technical and I don't feel up to the task of describing for each exactly what we need, what for, and why that project's current API is not good enough for us. So please edit the page and fix up the draft description I have put there. In particular this probably means Kai Blin and/or Juan Lang for the Samba stuff, and Alexandre Julliard, Dmitry Timoshkov or Mike McCormack to correct my weird window manager speculations.
And finally, what did I miss? Linux thread priorities? Anything on the sound side? Anything on the X server side?
Francois Gouget wrote:
And finally, what did I miss? Linux thread priorities? Anything on the sound side? Anything on the X server side?
The fact that Free/Open/BSD exist.
On Thu, 27 Apr 2006, Segin wrote:
Francois Gouget wrote:
And finally, what did I miss? Linux thread priorities? Anything on the sound side? Anything on the X server side?
The fact that Free/Open/BSD exist.
Uh? What do you mean? That Free/Open/BSD should be changed in order to run Wine? what changes would be needed?
On Thu, Apr 27, 2006 at 06:36:09PM +0200, Francois Gouget wrote:
So I created a Wiki page to keep track of these features we would need from other projects to make Wine better. There are some *BIG* caveats though:
- The page is 'http://wiki.winehq.org/WineWishes'.
What you describe seems to exist already at: http://wiki.winehq.org/IntegrationProjects
Or did I miss anyhting?
Jan
I believe an X extension is needed to completely solve bug 1410: http://bugs.winehq.org/show_bug.cgi?id=1410
On windows, when dinput listens for relative mouse movement, it does so without affecting the cursor's position. Wine implements relative mouse movement by constantly recentering the cursor on the window that requests it and watching it as it moves away from the center. In exclusive mode, this rarely causes problems as that combination makes it impossible to move the mouse on windows. Some apps request relative mouse movement in nonexclusive mode and expect the user to move the mouse normally (but the user can't because the mouse is always being recentered). If wine didn't recenter the mouse, it wouldn't be able to detect mouse input that would bring the mouse beyond the edge of the screen (which windows can do).
Windows probably pulls this off by reading relative mouse movement directly from the device, but I don't think wine developers want to go that route. An X extension would be needed that can detect relative mouse movement that does not generate absolute movement.
-- Vincent Povirk aka MadEwokHerd Primary email: madewokherd@gmail.com Secondary email: madewokherd@comcast.net Tertiary email: vrp5000@psu.edu Jabber: madewokherd@jabber.org
On Thu, Apr 27, 2006 at 02:35:14PM -0400, Vincent Povirk wrote:
Windows probably pulls this off by reading relative mouse movement directly from the device, but I don't think wine developers want to go that route. An X extension would be needed that can detect relative mouse movement that does not generate absolute movement.
Well, all (except tablets of course) mouse drivers report relative movements (even in X11 at the lowest level).
We just need to export this to user-space via the X11 API.
I once started a thread about this on the FD.O lists and people seemed to agree it would be doable and (if not too ugly) accepted into the X.org tree. Now we just need to find someone to code it :)
Lionel
On Thursday 27 April 2006 21:42, Lionel Ulmer wrote:
On Thu, Apr 27, 2006 at 02:35:14PM -0400, Vincent Povirk wrote:
Windows probably pulls this off by reading relative mouse movement directly from the device, but I don't think wine developers want to go that route. An X extension would be needed that can detect relative mouse movement that does not generate absolute movement.
Well, all (except tablets of course) mouse drivers report relative movements (even in X11 at the lowest level).
We just need to export this to user-space via the X11 API.
I once started a thread about this on the FD.O lists and people seemed to agree it would be doable and (if not too ugly) accepted into the X.org tree. Now we just need to find someone to code it :)
You, you already left too many time speaking about that, you would time to code it :)
Lionel
Raphael
PS: it'll be cool to have a GLX extension to change the "fbconfig" of an existing window and another to share contexts (ala wglShareLists)
You, you already left too many time speaking about that, you would time to code it :)
Not sure. I once debugged something in XFree and already spent hours understanding the code and this was only in a peripheric library (DGA). I can't even imagine the time it would take to go into the 'real' X core to understand how input works :-)
PS: it'll be cool to have a GLX extension to change the "fbconfig" of an existing window and another to share contexts (ala wglShareLists)
Well, better petition AJ to have the possibility to 're-create' on the fly the X window, it would be easier :-)
And you cannot share lists using glXCreateContext (the last parameter) ?
Lionel
On Thu, 27 Apr 2006, Jan Zerebecki wrote:
On Thu, Apr 27, 2006 at 06:36:09PM +0200, Francois Gouget wrote:
So I created a Wiki page to keep track of these features we would need from other projects to make Wine better. There are some *BIG* caveats though:
- The page is 'http://wiki.winehq.org/WineWishes'.
What you describe seems to exist already at: http://wiki.winehq.org/IntegrationProjects
Or did I miss anyhting?
Indeed there is some overlap, this page mixes two aspects: * how to change Wine to better integrate with the rest of the system * how to other projects should be modified to help Wine work better or better integrate with them
Though it is predominently about the first aspect. For instance the SingleSignOn entry talks about the work done on Wine to improve single sign-on, not whether or not we need some Samba code relicensed or some API defined, etc.
Should I just merge the contents of what I have in WineWishes with that page? Or would it be better to separate those two aspects? If the former I think it would be nice to at least clearly identify items that require changes outside of Wine.
On Fri, Apr 28, 2006 at 06:57:09PM +0200, Francois Gouget wrote:
On Thu, 27 Apr 2006, Jan Zerebecki wrote:
On Thu, Apr 27, 2006 at 06:36:09PM +0200, Francois Gouget wrote:
- The page is 'http://wiki.winehq.org/WineWishes'.
What you describe seems to exist already at: http://wiki.winehq.org/IntegrationProjects
Or did I miss anyhting?
Indeed there is some overlap, this page mixes two aspects:
- how to change Wine to better integrate with the rest of the system
- how to other projects should be modified to help Wine work
better or better integrate with them
Should I just merge the contents of what I have in WineWishes with that page? Or would it be better to separate those two aspects? If the former I think it would be nice to at least clearly identify items that require changes outside of Wine.
As most changes to something outside of Wine also require changes in Wine I think it's best to have them on one page and as you say clearly identify those outside items. Whatever you choose, it is nice to avoid duplication.
Jan
-
Francois Gouget -
Jan Zerebecki -
Lionel Ulmer -
Raphael -
Segin -
Vincent Povirk