20,741
edits
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{Template:RFC Navigation}} | {{Template:RFC Navigation}} | ||
= FlightGear Headless = | = FlightGear Headless = | ||
== Status (10/2012) == | |||
As of 10/2012, this is being worked on (also see [[FlightGear Run Levels]]): | |||
{{cquote|I'm working on a prototype of this - with no X11 / VLC required at all. It will load scenery tiles (for ground-intersections) but no views or rendering. But don't be in a rush for something to appear in Git, it's just an experiment.<ref>{{cite web |url=https://code.google.com/p/flightgear-bugs/issues/detail?id=882 |title=Issues 882 (Improved CI / regression testing support by providing options to disable interactive features (sound/window))|author=James Turner |date=Sep 26, 2012}}</ref>|James Turner}} | |||
{{cquote|Make subsystems create-able and removable from commands. Only some subsystems are supported so far, since many have non-default constructors or other complexities. | |||
With this, change, it's possible to dynamically add and remove the traffic-manager at runtime, for example: fgcommand("add-subsystem", props.Node.new({ "subsystem": "traffic-manager", "name":"traffic-manager", "do-bind-init":1}));<ref>{{cite web |url=https://gitorious.org/fg/flightgear/commit/8608a480736651999c5ea31a489343ee097ee915 |title=Initial work on dynamic subsystem creation.|author=James Turner |date=Oct 01, 2012}}</ref>|James Turner}} | |||
<references/> | |||
== Regression Testing in FlightGear == | == Regression Testing in FlightGear == | ||
Line 77: | Line 90: | ||
* [[Howto:Extending Nasal|extend the Nasal API]] in order to facilitate "remote controlling" the simulator largely using scripts | * [[Howto:Extending Nasal|extend the Nasal API]] in order to facilitate "remote controlling" the simulator largely using scripts | ||
[[Category: | [[Category:Core Development Projects]] |