Modernizing FlightGear Scripting: Difference between revisions

 
Line 371: Line 371:


== The current situation ==
== The current situation ==
*If* you want embedded scripting with hooks inside flightgear, and you don't want nasal, then you are probably on your own with that.  When we discussed this previously we decided that we didn't want to encourage multiple optional script engines because of the chances people will create aircraft with dependencies that no one else has and also the extra complexity of maintaining multiple script engines in the core code.<ref>{{cite web
  |url    =  https://forum.flightgear.org/viewtopic.php?p=296534#p296534
  |title  =  <nowiki> Re: Why not use Erlang instead of  </nowiki>
  |author =  <nowiki> curt </nowiki>
  |date  =  Oct 11th, 2016
  |added  =  Oct 11th, 2016
  |script_version = 0.40
  }}</ref>
We have a single SGSubsystemMgr based FGNasalSys class inherited from SGSubsystem, which implements support for FlightGear scripting (add references/links below):
We have a single SGSubsystemMgr based FGNasalSys class inherited from SGSubsystem, which implements support for FlightGear scripting (add references/links below):