20,741
edits
Startup Modes: Difference between revisions
Jump to navigation
Jump to search
m
→Implementation
m (→Implementation) |
m (→Implementation) |
||
| Line 68: | Line 68: | ||
== Implementation == | == Implementation == | ||
The implementation is surprisingly straightforward, as long as it's based on the approach used by Torsten and Florent to implement the [[Addons]] system, and in line with the method used by Erik to implement [[Graphics Card Profiles]] support. | The implementation is surprisingly straightforward, as long as it's based on the approach used by Torsten and Florent to implement the [[Addons]] system, and it would be in line with the method used by Erik to implement [[Graphics Card Profiles]] support. | ||
We are also already using the same mechanism to support custom scenery overlays and custom aircraft directories. | |||
So, startup modes could for example be stored in $FG_ROOT/Modes, using a custom set of directories with PropertyList/XML overlays, these would take precedence over files loaded from $FG_ROOT, e.g. : | |||
* defaults.xml (formerly, preferences.xml) | * defaults.xml (formerly, preferences.xml) | ||
| Line 78: | Line 80: | ||
(and possibly even options.xml) | (and possibly even options.xml) | ||
This kind of setup would make it possible to easily include, and maintain, mutually-exclusive features in fgdata without adding tons of hard-coded logics/heuristics to deal with ALS vs. Rembrandt or aircraft vs. spacecraft configuration paths. | |||
== References == | == References == | ||
{{Appendix}} | {{Appendix}} | ||