20,741
edits
Unifying the 2D rendering backend via canvas: Difference between revisions
Jump to navigation
Jump to search
Unifying the 2D rendering backend via canvas (view source)
Revision as of 16:45, 6 July 2012
, 6 July 2012→Background
| Line 32: | Line 32: | ||
* agradar: https://gitorious.org/fg/flightgear/blobs/next/src/Instrumentation/agradar.cxx | * agradar: https://gitorious.org/fg/flightgear/blobs/next/src/Instrumentation/agradar.cxx | ||
* NavDisplay: https://gitorious.org/fg/flightgear/blobs/next/src/Instrumentation/NavDisplay.cxx | * NavDisplay: https://gitorious.org/fg/flightgear/blobs/next/src/Instrumentation/NavDisplay.cxx | ||
We need to take a look at these instruments and their C++ code, to ensure that the Canvas API is sufficiently customizable to implement these and similar instruments purely in scripting space. | |||
As of 07/2012 the navdb (including airports, runways etc) is fully exposed as part of the NasalPositioned module in $FG_SRC/Scripting: https://gitorious.org/fg/flightgear/blobs/next/src/Scripting/NasalPositioned.cxx | As of 07/2012 the navdb (including airports, runways etc) is fully exposed as part of the NasalPositioned module in $FG_SRC/Scripting: https://gitorious.org/fg/flightgear/blobs/next/src/Scripting/NasalPositioned.cxx | ||