Re: X developer's conference, April 16-18
Hi, I'm picking up that topic again. I lost the original mail, so I apologize for the lost in-reply-to references. I think we have a few topics to talk to the X people about. If nobody else volunteers I could go to the conference personally, however, I'd need some support financing the travel costs. However, I'm European, so it might work better for someone local in the US. A few proposed topics: * Relative mouse movements * A few new GL extensions. Only partially concerns Xorg, but I think it is reasonable to present them there in the hope that ATI, Nvidia and Mesa people are there. -> Flat shading vertex colors -> sRGB writing without blending -> Texture rectangles with normalized coords -> GLSL support for some D3D shader instructions(mova, lit) -> More widespread support for a few existing extensions * Other things?
Stefan Dösinger skrev:
A few proposed topics:
* Relative mouse movements * A few new GL extensions. Only partially concerns Xorg, but I think it is reasonable to present them there in the hope that ATI, Nvidia and Mesa people are there. -> Flat shading vertex colors -> sRGB writing without blending -> Texture rectangles with normalized coords -> GLSL support for some D3D shader instructions(mova, lit) -> More widespread support for a few existing extensions * Other things?
Did someone mention a nice way to query amount of video card's onboard VRAM?
Stefan Dösinger skrev:
A few proposed topics:
* Relative mouse movements * A few new GL extensions. Only partially concerns Xorg, but I think it is reasonable to present them there in the hope that ATI, Nvidia and Mesa people are there. -> Flat shading vertex colors -> sRGB writing without blending -> Texture rectangles with normalized coords -> GLSL support for some D3D shader instructions(mova, lit) -> More widespread support for a few existing extensions * Other things?
Did someone mention a nice way to query amount of video card's onboard VRAM?
I talked about that with some X developers a while ago and they felt (and I agree with them) that this is something that should not be exported. OpenGL hides it from us for a reason. It is against the philosophy of GL. DirectX allows it but the same as exporting the pci id, it is not something that should be exported in my opinion. Roderick -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
Am Montag, 25. Februar 2008 19:21:18 schrieb Roderick Colenbrander:
Did someone mention a nice way to query amount of video card's onboard VRAM?
I talked about that with some X developers a while ago and they felt (and I agree with them) that this is something that should not be exported. OpenGL hides it from us for a reason. It is against the philosophy of GL. DirectX allows it but the same as exporting the pci id, it is not something that should be exported in my opinion. There's GL_ATI_meminfo, but no spec about it. I think I found a way to find the current free video memory, but not the total one. The current free vidmem is comparably uninteresting because it is managed by opengl anyway and we cannot implement a proper D3DPOOL_DEFAULT pool due to that.
I haven't seen any equivalent to this on the nvidia side
On Monday 25 February 2008 17:49:42 Stefan Dösinger wrote:
* Other things?
Display settings at the window manager level: http://bugs.winehq.org/show_bug.cgi?id=3230 http://bugs.winehq.org/show_bug.cgi?id=10115 http://bugs.winehq.org/show_bug.cgi?id=10841
Am Dienstag, 26. Februar 2008 14:41:12 schrieb Tijl Coosemans:
On Monday 25 February 2008 17:49:42 Stefan Dösinger wrote:
* Other things?
Display settings at the window manager level:
http://bugs.winehq.org/show_bug.cgi?id=3230 http://bugs.winehq.org/show_bug.cgi?id=10115 http://bugs.winehq.org/show_bug.cgi?id=10841 Good point about that. I think 10115 needs to be done in the window manager, while 3230 and 10841 are Wine's business
On Tue, Feb 26, 2008 at 7:41 AM, Tijl Coosemans <tijl(a)ulyssis.org> wrote:
On Monday 25 February 2008 17:49:42 Stefan Dösinger wrote:
* Other things?
Display settings at the window manager level:
http://bugs.winehq.org/show_bug.cgi?id=3230 http://bugs.winehq.org/show_bug.cgi?id=10115 http://bugs.winehq.org/show_bug.cgi?id=10841
The right thing to do here is to create a specification for how this would work and bring it to wm-spec-list. Then you can at least count on metacity to add support for it, if wm-spec-list approves it. Then again, they might just tell you WINE is broken. -- Travis Watkins http://www.realistanew.com
participants (6)
-
Ove Kaaven -
Roderick Colenbrander -
Stefan Dösinger -
Stefan Dösinger -
Tijl Coosemans -
Travis Watkins