20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
→Canvas
m (→Canvas) |
(→Canvas) |
||
| Line 79: | Line 79: | ||
Once the [[Canvas Development#The_Future_of_Canvas_in_FlightGear|PropertyBasedElement/CanvasElement wrappers]] are fully exposed to scripting space, we could easily register MapStructure as a new Canvas element for directly making the corresponding layers available to C++ code, without introducing any direct Nasal dependencies - i.e. the corresponding airports/runway and taxiways diagrams would be transparently created by Nasal-based Canvas elements, with the Qt5/C++ code only ever having to set a handful of properties (airport ICAO id, styling, range etc). | Once the [[Canvas Development#The_Future_of_Canvas_in_FlightGear|PropertyBasedElement/CanvasElement wrappers]] are fully exposed to scripting space, we could easily register MapStructure as a new Canvas element for directly making the corresponding layers available to C++ code, without introducing any direct Nasal dependencies - i.e. the corresponding airports/runway and taxiways diagrams would be transparently created by Nasal-based Canvas elements, with the Qt5/C++ code only ever having to set a handful of properties (airport ICAO id, styling, range etc). | ||
The main obstacle preventing us from doing this right now is that we're not yet [[Initializing Nasal early]], so that the corresponding Nasal/Canvas bindings (via [[Nasal/CppBind]]) are not yet available when the Qt5 UI is running. | |||
=== PLIB/PUI (legacy GUI) === | === PLIB/PUI (legacy GUI) === | ||