20,741
edits
Howto:Reset/re-init Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
Howto:Reset/re-init Troubleshooting (view source)
Revision as of 16:26, 23 February 2016
, 23 February 2016→Objective
| Line 102: | Line 102: | ||
[[Reset & re-init]] is an effort to refactor the FlightGear initialization process so that resetting and repositioning (switching aircraft) is supported, without having to exit or restart FlightGear. Currently, this is exposed via the Canvas-based [[Aircraft Center]], but is considered broken or fragile at best by most core developers. | [[Reset & re-init]] is an effort to refactor the FlightGear initialization process so that resetting and repositioning (switching aircraft) is supported, without having to exit or restart FlightGear. Currently, this is exposed via the Canvas-based [[Aircraft Center]], but is considered broken or fragile at best by most core developers. | ||
The core developers are aiming to find out the dependencies of different subsystems<ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg18066.html</ref>, and re-factor them so that more and more subsystems can be made optional (analogous to [[FlightGear Run Levels|run-levels]])<ref>http://forum.flightgear.org/</ref>, enabling them to be dynamically removed and re-added at run-time. This will be particularly important to untangle implicit or hard-coded dependencies among the different subsystems, and will be one of the key tasks to move certain subsystems into dedicated [[High-Level Architecture]] (HLA) {{wikipedia|High-level architecture#Common HLA terminology|federates|noicon=1}}. | The core developers are aiming to find out the dependencies of different subsystems<ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg18066.html</ref>, and re-factor them so that more and more subsystems can be made optional (analogous to [[FlightGear Run Levels|run-levels]])<ref>http://forum.flightgear.org/</ref>, enabling them to be dynamically removed and re-added at run-time. | ||
This will be particularly important to untangle implicit or hard-coded dependencies among the different subsystems<ref>http://sourceforge.net/p/flightgear/mailman/message/34793948/</ref>, and will be one of the key tasks to move certain subsystems into dedicated [[High-Level Architecture]] (HLA) {{wikipedia|High-level architecture#Common HLA terminology|federates|noicon=1}}. | |||
One of the long-term goals is to provide a so called "[[FlightGear Headless|headless]]" mode so that certain features/subsystems (unrelated to graphics) can be better tested in isolation. An example would running FlightGear in an automated fashion on the [[FlightGear Build Server]], which could help increasingly automate the release process and related regression testing<ref>http://sourceforge.net/p/flightgear/mailman/message/34741767/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/34627074/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/34657550/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/34701971/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/34657898/</ref>. | One of the long-term goals is to provide a so called "[[FlightGear Headless|headless]]" mode so that certain features/subsystems (unrelated to graphics) can be better tested in isolation. An example would running FlightGear in an automated fashion on the [[FlightGear Build Server]], which could help increasingly automate the release process and related regression testing<ref>http://sourceforge.net/p/flightgear/mailman/message/34741767/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/34627074/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/34657550/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/34701971/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/34657898/</ref>. | ||