Complex Canvas avionics: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
Line 2: Line 2:


== Background ==
== Background ==
 
{{FGCquote
The airspace system is in the process of changing drastically, and I'm following it this summer by finally biting the bullet and installing an IFR GPS (Garmin GTN 650 <https://buy.garmin.com/en-CA/CA/p/67884>;) and ADS-B transponder (Garmin GTX 345 <https://buy.garmin.com/en-CA/CA/p/140949>;) in my Piper Warrior II. What this means that for the first time in the 15 years since I started flying in real life, I won't be able to use FlightGear to practice the IFR approaches I'm flying in real life.<ref>{{cite web
|1= The airspace system is in the process of changing drastically, and I'm following it this summer by finally biting the bullet and installing an IFR GPS (Garmin GTN 650) and ADS-B transponder (Garmin GTX 345) in my Piper Warrior II. What this means that for the first time in the 15 years since I started flying in real life, I won't be able to use FlightGear to practice the IFR approaches I'm flying in real life.
|2= {{cite web
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/35924395/  
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/35924395/  
   |title  =  <nowiki> [Flightgear-devel] RFD: FlightGear and the changing state of air
   |title  =  <nowiki> [Flightgear-devel] RFD: FlightGear and the changing state of air
Line 10: Line 11:
   |date  =  Jul 3rd, 2017  
   |date  =  Jul 3rd, 2017  
   |added  =  Jul 3rd, 2017  
   |added  =  Jul 3rd, 2017  
   |script_version = 0.40
   |script_version = 0.39
   }}</ref>
   }}
}}


== Objective ==
== Objective ==

Revision as of 08:53, 6 July 2017

This article is a stub. You can help the wiki by expanding it.

Background

Cquote1.png The airspace system is in the process of changing drastically, and I'm following it this summer by finally biting the bullet and installing an IFR GPS (Garmin GTN 650) and ADS-B transponder (Garmin GTX 345) in my Piper Warrior II. What this means that for the first time in the 15 years since I started flying in real life, I won't be able to use FlightGear to practice the IFR approaches I'm flying in real life.
Cquote2.png

Objective

Provide a summary of potential improvements to make the development of complex Canvas-based avionics feasible.

Ideas

  • Integrate Gijs' projection handling patches (see Map dialog)
  • Avoid/speed up property I/O
  • Implement support for symbol/element instancing (as per James' original comments)
  • Use native C++ code for animation handling instead of dozens of Nasal timers/listeners per element
  • Review Richard's MFD framework to make concepts like "screen", "page", "pageElement" first class concepts at the Canvas::Element/Canvas::Group level
  • state management should probably be handled by the corresponding SimGear state machine code and not tons of custom Nasal code
  • determine what may be missing in terms of new/optimized Canvas elements for special purposes (i.e. best using native C++ code instead of custom Nasal hacks), e.g.:

References

References