Property tree: Difference between revisions

Jump to navigation Jump to search
m (improve socket/telnet/http terminology)
Line 72: Line 72:
* internal compiled code within FG - the c/c++ code
* internal compiled code within FG - the c/c++ code
* [[Nasal]] scripts - this is javascript like scripting with read/write to the property tree. This is the way most aircraft are implemented.
* [[Nasal]] scripts - this is javascript like scripting with read/write to the property tree. This is the way most aircraft are implemented.
* Generic protocol sockets that are either in/out/bi - this allows send/receive to the FG sim via the generic protocol
* Using native protocols, implemented in C++ (see [https://gitorious.org/fg/flightgear/trees/next/src/Network $SG_SRC/Network]. [[Property Tree/Sockets]]
* Using the generic protocol, either in/out/bi - this allows send/receive to the FG sim via the [[Generic Protocol]]
* telnet interface - query and fly the plane on the command line (see [[Telnet usage]])
* telnet interface - query and fly the plane on the command line (see [[Telnet usage]])
* html interface - fly the plane with a browser or an PDA
* html interface - fly the plane with a browser or an PDA
For example, multiplayer mode is accomplished by exchanging sets of variables from the tree (height, position, speed, etc).
For example, multiplayer mode is accomplished by exchanging sets of variables from the tree (height, position, speed, etc).


== Flight Dynamics Model (FDM) ==
== Flight Dynamics Model (FDM) ==

Navigation menu