On Wed, Dec 04, 2002 at 01:57:48PM -0700, Nicholas Leippe wrote: > It seems as if none of the levels of controls people have been asking for in > this thread can't be satisfied via environment variables in one way or > another--it seems to be the most flexible solution.
The problem with env vars is that if they change (or new ones are added, or old ones removed, or the user changes hardware, or ...) all of the scripts that set them have to change. It's not un-manageable, but it would be a fair amount of work. Now, imagine the drivers having an interface that a tool (for creating app. profiles) could query. The driver would send back (perhaps using XML or something similar?) a list of "knobs" that is has in the form: - Short name - Long description - Type (boolean, range, etc.) - Default value (perhaps as mandated by the OpenGL standard) The tool could be something as simple as a shell utility to tell the user what options are available for the driver. That would be a step up from the current 'grep getenv xc/xc/lib/GL/mesa/src/drv/<driver name>/*.c'. :) It would also save us from having to maintain a web page of all the different env vars for each driver. Internationalization would be a problem, though. The neat thing is that if other (close source) drivers supported the query interface & config file format, they could use the same tool. I don't see how you could do the same with a wrapper library. How could the wrapper know how to disable some extension in the Nvidia driver? -- Smile! http://antwrp.gsfc.nasa.gov/apod/ap990315.html ------------------------------------------------------- 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
