198b88ca9b
scene management code and organizing it within simgear. My strategy is to identify the code I want to move, and break it's direct flightgear dependencies. Then it will be free to move over into the simgear package. - Moved some property specific code into simgear/props/ - Split out the condition code from fgfs/src/Main/fg_props and put it in it's own source file in simgear/props/ - Created a scene subdirectory for scenery, model, and material property related code. - Moved location.[ch]xx into simgear/scene/model/ - The location and condition code had dependencies on flightgear's global state (all the globals-> stuff, the flightgear property tree, etc.) SimGear code can't depend on it so that data has to be passed as parameters to the functions/methods/constructors. - This need to pass data as function parameters had a dramatic cascading effect throughout the FlightGear code. |
||
|---|---|---|
| .. | ||
| .cvsignore | ||
| electrical.cxx | ||
| electrical.hxx | ||
| Makefile.am | ||
| pitot.cxx | ||
| pitot.hxx | ||
| README | ||
| static.cxx | ||
| static.hxx | ||
| system_mgr.cxx | ||
| system_mgr.hxx | ||
| vacuum.cxx | ||
| vacuum.hxx | ||
src/Systems/ - support code for aircraft systems This directory contains support code for major aircraft systems, including the static, pitot, electrical, and vacuum systems. The file system_mgr.[ch]xx contains a subsystem group that holds all of the individual systems. Every system should extend FGSubsystem, and then should be added to the group in the FGSystemMgr constructor. Eventually, there will be an XML configuration file to select what system modules should be available, so that different aircraft (i.e. a twin plane with two vacuum systems) can have appropriate support.