I try to figure out these things using the database of the OpenGL extensions viewer: http://www.realtech-vr.com/glview/
It is not the best, as its database is far from complete but may help in some cases.
Sounds interesting, but does not work at me (the applet does not show up after Java load).
Sorry that I cannot help any more but you can add me to the list of interested people in the topic as I also agree that sometimes it is quite a burden to figure out what is supported on earlier hardware and what not.
The thing is that it’s quite easy to develop an application to collect the information. Using a Java applet isn’t the best way. The old Delphi3D.net site had you download and run a program that would automatically upload your information to its database. Writing a simple tool to collect this information is pretty simple.
Actually using it is not. Storing it in a database, using that database to generate web pages, etc. That is the hard stuff. Or at least, it’s hard for me.
I never underestimate how dumb I can be, how dumb a developer can be, how dumb a user can be. Being dumb is the human nature, that’s ok.
If it could work properly, a web-app seams to me to be the easiest way and building this database online is not tricky at all for someone with even a limited skill on that area.
I think that having an updated database of OpenGL versions and extensions support could contribute to modern OpenGL adoption…
Then the drivers need to be a bit reliable… Back in the days, I remember official Intel drivers claiming VBO support (within the extensions string) but returning null pointers to all the entry points… I don’t know if such practice remains at Intel but my guess it does.
If all you want to do is test the code paths of your app that do different things based on what extensions are available, GLIntercept has a plugin to add/remove or even replace the entire extension string.
I used it for exactly this purpose. However, the modern OpenGL extension query system is not yet supported in GLIntercept.
I’m glad you like it. My immediate goal is just to report the system’s OpenGL capabilities without requiring administrator privelages or an actual install (I suppose the applet is installed). If the community is interested in using it to create a database, I am all for it and am happy to open the project up to other developers. In the near term (say next three months), I am too swamped to take it on myself.
I’d urge anyone interested in a database of OGL capabilites to visit and use the tool. You need to install Java if you don’t have it.
It’s far from perfect, but’s it’s a step in the right direction. It would be nice to be able to search on a specific glGet parameter to find out which card/driver combos support what, but its usable as is.