2,561
edits
Talk:Backwards Compatibility Initiative: Difference between revisions
Jump to navigation
Jump to search
m
Talk:Backwards Compatibility Initiative (view source)
Revision as of 13:07, 16 March 2010
, 16 March 2010→Requirements for a flexible Compatibility Scheme in FG
m (requirements for a flexible compatibiltiy scheme in FG) |
|||
| Line 10: | Line 10: | ||
Exposing modifications to internal APIs via the property tree enables FlightGear resources such as XML files or Nasal scripts to dynamically adjust to the runtime environment: | Exposing modifications to internal APIs via the property tree enables FlightGear resources such as XML files or Nasal scripts to dynamically adjust to the runtime environment: | ||
* the base package may need to be provided with version info for relevant commits so that the executable can check for a matching package, this is a frequently brought up issue -because users may need to manually check if binaries and base package match | |||
* expose library versions (OSG, SimGear ...) and build/config settings via property tree | * expose library versions (OSG, SimGear ...) and build/config settings via property tree | ||
* expose full list of fgfs startup parameters and runtime variables via property tree | * expose full list of fgfs startup parameters and runtime variables via property tree | ||