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 | ||
| fgjs.cxx | ||
| input.cxx | ||
| input.hxx | ||
| js_demo.cxx | ||
| jsinput.cxx | ||
| jsinput.h | ||
| jssuper.cxx | ||
| jssuper.h | ||
| Makefile.am | ||