Canvas news: Difference between revisions

Jump to navigation Jump to search
Line 47: Line 47:
   }}</ref>
   }}</ref>


 
For starters, Stuart is hoping to to optimize the property access and become more familiar with the Canvas C++ code so that he can help bridge the cap between core and Canvas client developers.  He thinks James has some thoughts on the Canvas C++, so he'll want to coordinate with him as well.<ref>{{cite web
 
Stuart is hoping to to optimize the property access and become more familiar with the Canvas C++ code so that he can help bridge the cap between core and Canvas client developers.  He thinks James has some thoughts on the Canvas C++, so he'll want to coordinate with him as well.<ref>{{cite web
   |url    =  https://forum.flightgear.org/viewtopic.php?p=313787#p313787  
   |url    =  https://forum.flightgear.org/viewtopic.php?p=313787#p313787  
   |title  =  <nowiki> Re: zkv1000 reborn </nowiki>  
   |title  =  <nowiki> Re: zkv1000 reborn </nowiki>  
Line 55: Line 53:
   |date  =  Jul 6th, 2017  
   |date  =  Jul 6th, 2017  
   |added  =  Jul 6th, 2017  
   |added  =  Jul 6th, 2017  
  |script_version = 0.40
  }}</ref>
One of the ideas raised by David is, should there maybe be a separate project to build an embeddable GPS navigator with different faces/UIs (and a default standalone front end)? As others have mentioned, a lot of the backend logic is the same, like doing a gradual transition from RNAV to Localiser on intercept to avoid a sudden jolt in the A/P, or calculating a turn past a fly-by waypoint. Again, that would be a way to join forces with other Sim dev communities. <ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35929948/
  |title  =  <nowiki> Re: [Flightgear-devel] RFD: FlightGear and the changing state of
air navigation </nowiki>
  |author =  <nowiki> David Megginson </nowiki>
  |date  =  Jul 5th, 2017
  |added  =  Jul 5th, 2017
   |script_version = 0.40  
   |script_version = 0.40  
   }}</ref>
   }}</ref>

Navigation menu