Nasal HLA standalone: Difference between revisions

Nasal HLA standalone (view source)

834 bytes removed , 27 May 2013

m

20,741

edits

@@ Line 9: / Line 9: @@
 This article will serve as the guinea pig for writing [[Developing with HLA]], using [[FlightGear HLA support (High Level Architecture)]].
-{{cquote|There is no simple mapping between FlightGear and FOM parameters. Sometimes it's necessary to translate units, geodetic/geocentric frames or perform other calculations. The generic mapping engine would have to be a very powerful scripting language like Nasal or Python.I've decided to start with a simple hardcoded interface and investigate all FOM attributes and interactions that may be supported by FlightGear/HLA. After we understand all possible features of the FlightGear/HLA interface, we will reconsider implementing the generic interface.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg22711.html|title=<nowiki>Re: [Flightgear-devel] [RFC] Dynamic plug-in interface for	I/Omodules</nowiki>|author=Petr Gotthard|date=Wed, 01 Jul 2009 07:31:44 -0700}}</ref>|Petr Gotthard}}
 {{cquote|Another thing that would work well is to proxy all nasal script invocations to a Nasal helper thread - again this assumes scripts