OpenGL 2.3 to 3.0
mclark4386 at charter.net
Tue Jun 5 15:26:37 CDT 2007
Ah this makes perfect sense and is exactly what I was looking for, thank
you for your response! My limited understanding from the article was
that 2.3 was simply cleanup and putting some extensions in the official
API that have been in drivers for a while just not in the official API
and then 3.0 is where the real change will be, BUT that it will only
activate the 3.0 functionality if it's on supporting hardware(i.e. DX10
cards). Please correct me if my understanding is incorrect and again I
think we all realize this is all in the future and is just fun to talk
Thanks for all THE fish,
PS Yes I am an idiot some times =P
> Stefan Dösinger wrote:
>> We are waiting for the final API before deciding if we like it or not. But
>> from what I've read so far the changes make sense.
>> My concern is backwards compatiblity. For dx 1 to dx9 we will still need the
>> old apis. For one part because the new api may not offer fixed function
>> functionality, but more importantly because old cards will most likely not
>> see any driver updates.
>> If the interface is vastly different we'll need 2 d3d implementations, one
>> wrapping to old gl and one for the new version. An idea would be to just
>> leave dx1 to 9 with gl 2.0 and write dx10 only for opengl 3.0.
>> If the new API allows it however, we want to keep the wine code unified. This
>> could happen by simply duplicating very specific functions which are
>> different, and then select them at creation time by choosing a different
>> virtual function table. If we need an if condition for every opengl call we
>> do it would be pointless to keep everything in one lib.
>> But we need to know the final opengl 3.0 API to decide what to do.
More information about the wine-devel