Re: Re: Wine 1.0 Tasks

Hi,
> > (Note the #3902 should be renamed as 'DIB Engine rewrite'
>
> Agreed; done.  http://bugs.winehq.org/show_bug.cgi?id=3902

:)
> > and i don't think is mandatory for 1.0)
>
> Probably right.  Let's create the next milestone after 1.0, say 1.1, and start
> retargeting bugs we don't plan to fix for 1.0.  (That's what GCC does;
> some bugs they retarget early, some just before the release.)
> > But i think we must fix users most hated bugs as:
> > - dsound deadlocks/craps
> > - openGL problems (multi contexts, fb/visual configs)
> > - lotus problems
>
> The OpenGL child window bug,
> http://bugs.winehq.org/show_bug.cgi?id=2398
> probably won't be fixed for 1.0 because it requires
> an X server change.

No it must be doable without X changes
(But X additions as GLX_EXT_texture_from_pixmap will help a lot).
Only problem is to find time to fix it (as lionel, i have no time for now).
Anyway i having a simple and downloadable application to reproduce this problem (not lightwave) must help.

The only parts who really needs X change are for:
 - glShareList: sharing fb/visual config between exitings GLX contexts 
 - dinput mouse management
> I'm not sure lotus notes problems should block 1.0, as IBM has a native
> Linux client now, but if someone wants to fix them (especially the ones
> in usp10.dll netapi32.dll, that would be great.

agree :)
> > Note: it will be interesting to add user votes to wine-bugs (ala kde) to
> > better see user needs.
>
> There are already user votes in bugzilla, that should suffice.
> - Dan

Oups i never seen it :)

Regards,
Raphael

Wine 1.0 Tasks

[Dan Kegel]

On 5/30/06, [e-mail]  wrote:
> > The OpenGL child window bug,
> > http://bugs.winehq.org/show_bug.cgi?id=2398
> > probably won't be fixed for 1.0 because it requires
> > an X server change.
>
> No it must be doable without X changes

It might be, but the heavy hitters I know of who have taken a look at
it in detail have concluded that an X change really is needed.
> (But X additions as GLX_EXT_texture_from_pixmap will help a lot).
> Only problem is to find time to fix it (as lionel, i have no time for now).
> Anyway i having a simple and downloadable application to reproduce this problem (not lightwave) must help.

There are already simple test apps linked to from
http://wiki.winehq.org/OpenGL
> The only parts who really needs X change are for:
> - glShareList: sharing fb/visual config between exitings GLX contexts
> - dinput mouse management

Are those 1.0 blockers?
- Dan

Wine 1.0 Tasks

[Raphael]

On Tuesday 30 May 2006 16:19, Dan Kegel wrote:
> On 5/30/06, [e-mail]  wrote:
> > > The OpenGL child window bug,
> > > http://bugs.winehq.org/show_bug.cgi?id=2398
> > > probably won't be fixed for 1.0 because it requires
> > > an X server change.
> >
> > No it must be doable without X changes
>
> It might be, but the heavy hitters I know of who have taken a look at
> it in detail have concluded that an X change really is needed.
> > (But X additions as GLX_EXT_texture_from_pixmap will help a lot).
> > Only problem is to find time to fix it (as lionel, i have no time for
> > now). Anyway i having a simple and downloadable application to reproduce
> > this problem (not lightwave) must help.
>
> There are already simple test apps linked to from
> http://wiki.winehq.org/OpenGL
> > The only parts who really needs X change are for:
> > - glShareList: sharing fb/visual config between exitings GLX contexts
> > - dinput mouse management
>
> Are those 1.0 blockers?

For the first no
For the second need users request (but it only impact games)
> - Dan

Regards,
Raphael

Wine 1.0 Tasks

[Scott Ritchie]

On Tue, 2006-05-30 at 07:19 -0700, Dan Kegel wrote:
> On 5/30/06, [e-mail]  wrote:
> > > The OpenGL child window bug,
> > > http://bugs.winehq.org/show_bug.cgi?id=2398
> > > probably won't be fixed for 1.0 because it requires
> > > an X server change.
> >
> > No it must be doable without X changes
>
> It might be, but the heavy hitters I know of who have taken a look at
> it in detail have concluded that an X change really is needed.]

Is this really a problem?  Another version of X is due out in about 4
months (probably the earliest we could possibly see Wine 1.0), so why
can't we just help write an X extension to tackle the bug?

Thanks,
Scott Ritchie

Wine 1.0 Tasks

[Dan Kegel]

On 5/30/06, Scott Ritchie  wrote:
> > It might be, but the heavy hitters I know of who have taken a look at
> > it in detail have concluded that an X change really is needed.]
>
> Is this really a problem?  Another version of X is due out in about 4
> months (probably the earliest we could possibly see Wine 1.0), so why
> can't we just help write an X extension to tackle the bug?

Not really a problem.  It'll just take some time to trickle out to the world.
We may also have to get Nvidia and ATI on board so they can implement
the extension in their drivers.
- Dan

Wine 1.0 Tasks

[Lionel Ulmer]

On Tue, May 30, 2006 at 05:32:26PM -0700, Dan Kegel wrote:
> On 5/30/06, Scott Ritchie  wrote:
> > > It might be, but the heavy hitters I know of who have taken a look at
> > > it in detail have concluded that an X change really is needed.]
> >
> > Is this really a problem?  Another version of X is due out in about 4
> > months (probably the earliest we could possibly see Wine 1.0), so why
> > can't we just help write an X extension to tackle the bug?
>
> Not really a problem.  It'll just take some time to trickle out to the world.
> We may also have to get Nvidia and ATI on board so they can implement
> the extension in their drivers.

And for it to be taken, I guess we would need to not only write the
extension, but a 'reference implementation' (I would guess in DRI / Mesa)
and get it approved by the FD.o people.

But ohsix's idea to use 'real' X windows 'overlaid' over the single Wine X
window would be the easiest idea to investigate (because it would not only
fixes this issue but also the mutiple windows with multiple pixel formats
problem that the former 'extension' solution does not).

Lionel (in 'not even time to read wine-devel' mode :-) )

Wine 1.0 Tasks

[Wino Rojo]

Lionel,

Where can I learn more about ohsix's idea (i.e. thread in which mail list)?

Thanks,

W.
> From: Lionel Ulmer 
> To: Dan Kegel 
> CC: [e-mail], "[e-mail]" 
> ,[e-mail]
> Subject: Re: Re: Wine 1.0 Tasks
> Date: Fri, 2 Jun 2006 21:27:53 +0200
>
> But ohsix's idea to use 'real' X windows 'overlaid' over the single Wine X
> window would be the easiest idea to investigate (because it would not only
> fixes this issue but also the mutiple windows with multiple pixel formats
> problem that the former 'extension' solution does not).
>      Lionel (in 'not even time to read wine-devel' mode :-) )
>
> --
>    	 Lionel Ulmer - http://www.bbrox.org/

_________________________________________________________________
Take charge with a pop-up guard built on patented Microsoft® SmartScreen 
Technology  
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI... 
  Start enjoying all the benefits of MSN® Premium right now and get the 
first two months FREE*.

Wine 1.0 Tasks

[Alexandre Julliard]

Lionel Ulmer  writes:
> But ohsix's idea to use 'real' X windows 'overlaid' over the single Wine X
> window would be the easiest idea to investigate (because it would not only
> fixes this issue but also the mutiple windows with multiple pixel formats
> problem that the former 'extension' solution does not).

That can't work, unless you want to go back to the old window
management implementation; but then you'll have to volunteer to solve
all the painting bugs yourself, I'm not doing this a second time ;-)

Wine 1.0 Tasks

[Huw Davies]

On Tue, May 30, 2006 at 04:11:41PM +0200, [e-mail] wrote:
> > The OpenGL child window bug,
> > http://bugs.winehq.org/show_bug.cgi?id=2398
> > probably won't be fixed for 1.0 because it requires
> > an X server change.
>
> No it must be doable without X changes
> (But X additions as GLX_EXT_texture_from_pixmap will help a lot).

How does this help?

Thanks,
Huw.

Wine 1.0 Tasks

[Raphael]

On Tuesday 30 May 2006 16:27, Huw Davies wrote:
> On Tue, May 30, 2006 at 04:11:41PM +0200, [e-mail] wrote:
> > > The OpenGL child window bug,
> > > http://bugs.winehq.org/show_bug.cgi?id=2398
> > > probably won't be fixed for 1.0 because it requires
> > > an X server change.
> >
> > No it must be doable without X changes
> > (But X additions as GLX_EXT_texture_from_pixmap will help a lot).
>
> How does this help?

http://people.freedesktop.org/~davidr/GLX_EXT_texture_from_pixmap.txt

they are better than FBO for this specific need.
Anyway for using it, we need a lot of modifications on x11drv (in the fameous 
window management code) acting as a composing manager.

Note: it will help a lot to provide a DIB engine not dependant to X 
limitations
> Thanks,
> Huw.

Regards,
Raphael

Wine 1.0 Tasks

[David Goodenough]

[e-mail] wrote:
> Hi,
> > > (Note the #3902 should be renamed as 'DIB Engine rewrite'
> >
> > Agreed; done.  http://bugs.winehq.org/show_bug.cgi?id=3902
>
> :)
> > > and i don't think is mandatory for 1.0)
> >
> > Probably right.  Let's create the next milestone after 1.0, say 1.1, and
> > start
> > retargeting bugs we don't plan to fix for 1.0.  (That's what GCC does;
> > some bugs they retarget early, some just before the release.)
> > > But i think we must fix users most hated bugs as:
> > > - dsound deadlocks/craps
> > > - openGL problems (multi contexts, fb/visual configs)
> > > - lotus problems
> >
> > The OpenGL child window bug,
> > http://bugs.winehq.org/show_bug.cgi?id=2398
> > probably won't be fixed for 1.0 because it requires
> > an X server change.
>
> No it must be doable without X changes
> (But X additions as GLX_EXT_texture_from_pixmap will help a lot).
> Only problem is to find time to fix it (as lionel, i have no time for
> now). Anyway i having a simple and downloadable application to reproduce
> this problem (not lightwave) must help.
>
> The only parts who really needs X change are for:
> - glShareList: sharing fb/visual config between exitings GLX contexts
> - dinput mouse management
> > I'm not sure lotus notes problems should block 1.0, as IBM has a native
> > Linux client now, but if someone wants to fix them (especially the ones
> > in usp10.dll netapi32.dll, that would be great.
>
> agree :)

Not sure this is quite true.  They are promising a native client for the
next release of Notes, it is called Hannover, and it is built on the 
Eclipse Rich Client Platform in Java.  But there is not one today that
I am aware of.

The next release is not due until early 2007 if I remember correctly.  So
it all depends on when 1.0 is due.

David
> > > Note: it will be interesting to add user votes to wine-bugs (ala kde) to
> > > better see user needs.
> >
> > There are already user votes in bugzilla, that should suffice.
> > - Dan
>
> Oups i never seen it :)
>
> Regards,
> Raphael

Wine 1.0 Tasks

[Wino Rojo]

Raphael,

I wrote a simple OpenGL app to test the glShareList problem. You can find it 
in my bug report:

http://bugs.winehq.org/show_bug.cgi?id=4945

Cheers,

Wino
> From: [e-mail]
> To: [e-mail]
> CC: [e-mail]
> Subject: Re: Re: Wine 1.0 Tasks
> Date: Tue, 30 May 2006 16:11:41 +0200
>
> Anyway i having a simple and downloadable application to reproduce this 
> problem (not lightwave) must help.
>
> The only parts who really needs X change are for:
> - glShareList: sharing fb/visual config between exitings GLX contexts
> - dinput mouse management
>
> Regards,
> Raphael

_________________________________________________________________
MSN® Calendar keeps you organized and takes the effort out of scheduling 
get-togethers. 
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI... 
  Start enjoying all the benefits of MSN® Premium right now and get the 
first two months FREE*.