magenta wrote:
I agree. Building upon the OpenGL API itself and adding extensions when necessary helps application developers address these capabilities and tradeoffs. Most of the "environment" setting tradeoffs are to address short comings that an application didn't handle for one reason or another. Messaging the OpenGL stream itself represents a way to address these "temporary" short comings in a non-intrusive manner. Want to override the default behavior of your favorite application? Just create a new Chromium SPU. At a basic level, Chromium is a fancy wrapper infrastructure on steroids. This solution even works when running on a closed source OpenGL implementation.See, the wrapper wouldn't have to communicate directly to the driver in order to do any of what's been discussed - it would override it *based on user preferences* using the existing high-level functionality provided by OpenGL itself.
Interesting enough, if the application developer notices there are some popular modifications being done to their OpenGL stream, it's much easier for him to incorporate these mods in their next version or update of the application than it is to deal with an ever increasing combination of environment settings.
--
/\
Jens Owen / \/\ _
[EMAIL PROTECTED] / \ \ \ Steamboat Springs, Colorado
-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
