2,561
edits
Recommended Property Tree Enhancements: Difference between revisions
Recommended Property Tree Enhancements (view source)
Revision as of 17:25, 16 March 2010
, 16 March 2010→Today's Practice
| Line 8: | Line 8: | ||
Thus, data flow dependencies need to be formalized and made '''explicit''' [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg18066.html] in order to help FlightGear become more structured in its housekeeping department. Implementing these suggestions will automatically also help in other areas that are currently limited by FlightGear's current model of internal state management, such as for example by making it easier to implement support for dynamically switchable aircraft (for details, see [[FlightGear Sessions]]). | Thus, data flow dependencies need to be formalized and made '''explicit''' [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg18066.html] in order to help FlightGear become more structured in its housekeeping department. Implementing these suggestions will automatically also help in other areas that are currently limited by FlightGear's current model of internal state management, such as for example by making it easier to implement support for dynamically switchable aircraft (for details, see [[FlightGear Sessions]]). | ||
In addition, this very meta information will also help make FlightGear more easily parallelizable: | |||
"In general, FG has quite a few data dependencies internally which make multi-threading challenging | |||
right now - there's groundwork to make the data-dependencies more explicit (i.e, via the property | |||
tree) that has to happen before pieces can easily move to other threads."[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg18066.html] | |||
== Problems == | == Problems == | ||