2119db35c3
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 | ||
acmodel.cxx | ||
acmodel.hxx | ||
loader.cxx | ||
loader.hxx | ||
Makefile.am | ||
model.cxx | ||
model.hxx | ||
modelmgr.cxx | ||
modelmgr.hxx | ||
panelnode.cxx | ||
panelnode.hxx | ||
README | ||
TODO |
Last updated $Date$ This directory contains code for loading, positioning, orienting, and animating 3D models. acmodel.cxx acmodel.hxx This module defines the FGAircraftModel subsystem, which manages the 3D model representing the aircraft the user is flying. model.cxx model.hxx This module defines the FG3DModel class, which represents any 3D model in the FlightGear world. modelmgr.cxx modelmgr.hxx This module defines the FGModelMgr subsystem, which manages all 3D models except for the aircraft.