20,741
edits
FlightGear Newsletter August 2012: Difference between revisions
FlightGear Newsletter August 2012 (view source)
Revision as of 12:16, 17 August 2012
, 17 August 2012→FlightGear Run-Levels
| Line 63: | Line 63: | ||
Recently, we were talking about implementing a standalone [[FGCanvas]] client, analogous to [[FGPanel]] - in order to be able to render [[Canvas]] instruments separately, on different computers. | Recently, we were talking about implementing a standalone [[FGCanvas]] client, analogous to [[FGPanel]] - in order to be able to render [[Canvas]] instruments separately, on different computers. | ||
However, obviously this new startup mode would not need many of the default subsystems, such as the FDM, sound, terrain etc. | However, obviously this new startup mode would not need many of the default subsystems, such as the FDM, sound, terrain etc. Many of these subsystems are initialized in a hard coded fashion so that they cannot currently be made optional even though they may not be stricly required. Also, for a very long time, it's never been possible to fully reset FlightGear properly, this makes many things difficult or even possible, including the [[FGCanvas]] idea. | ||
We have now started collecting ideas on how this could be changed, by making subsystem initialization more explicit using listeners, so that SGSubsystems can be dynamically allocated and freed based on setting signal properties, so that recursive run levels can be implemented. For more information, please see [[FlightGear Run Levels]]. | We have now started collecting ideas on how this could be changed, by making subsystem initialization more explicit using listeners, so that SGSubsystems can be dynamically allocated and freed based on setting signal properties, so that recursive run levels can be implemented. For more information, please see [[FlightGear Run Levels]]. Feedback welcome! | ||
=== Mailing list digest === | === Mailing list digest === | ||