20,741
edits
(→Idea) |
(→Idea) |
||
Line 33: | Line 33: | ||
Other contributors, like Thorsten mentioned, that it does not seem to be a technical problem - to query a string from the property tree is easy, to write a routine which sets other properties based on what the string says is equally easy. | Other contributors, like Thorsten mentioned, that it does not seem to be a technical problem - to query a string from the property tree is easy, to write a routine which sets other properties based on what the string says is equally easy. | ||
The problem is the meat of it - someone has to know what settings are likely to run on what graphics cards. And someone has to write the routine that does it. Then it's done. <ref>{{cite web | The problem is the meat of it - someone has to know what settings are likely to run on what graphics cards. And someone has to write the routine that does it. Then it's done. <ref>{{cite web | ||
| url = http://forum.flightgear.org/viewtopic.php?p=275312#p275312 | | url = http://forum.flightgear.org/viewtopic.php?p=275312#p275312 | ||
Line 53: | Line 54: | ||
</ref> : | </ref> : | ||
[[File:Sigar-support.png|250px|[[Resource Tracking for FlightGear]]]] | |||
For example, $FG_ROOT/gui/dialogs/about.xml and rendering.xml are already accessing some of the GL* data via properties, e.g. to display the Intel warning, but also the GPU vendor info: | For example, $FG_ROOT/gui/dialogs/about.xml and rendering.xml are already accessing some of the GL* data via properties, e.g. to display the Intel warning, but also the GPU vendor info: | ||
[[File:About dialog 2.10.png|250px|[[About dialog]] ]] | |||
Thus, we would ideally introduce 3-4 "vendor"-specific folders and then introduce a PropertyList XML file where the RENDERER string is used to select a certain default configuration. | Thus, we would ideally introduce 3-4 "vendor"-specific folders and then introduce a PropertyList XML file where the RENDERER string is used to select a certain default configuration. |