20,741
edits
FlightGear run levels: Difference between revisions
Jump to navigation
Jump to search
→Problem
| Line 14: | Line 14: | ||
In other words, to reuse the FlightGear binary for other purposes, such as a standalone [[FGPanel]]/[[FGCanvas]] mode or a standalone ATC client, requires some refactoring in order to make subsystem initialization optional and fully runtime-configurable. | In other words, to reuse the FlightGear binary for other purposes, such as a standalone [[FGPanel]]/[[FGCanvas]] mode or a standalone ATC client, requires some refactoring in order to make subsystem initialization optional and fully runtime-configurable. | ||
Also, this work should align well with other currently ongoing plans, such as for example decoupling the viewer from the rest of the simulation loop: | |||
{{cquote|I understand the idea behind the 'fgviewer' tool as creating a distinct viewer component (yet still in the early stage of development) which, while still remaining compilant with the FlightGear environment, is trying to adopt as little dependencies from FlightGear as possible and therefore does not necessarily has to follow every rule of "how things are done in fgfs" in order to achieve its fine goal. | |||
Actually I'm convinced that carefully cutting some of the old ties (some call them "cruft"), for example by keeping the viewer part as independent from the FlightGear core as possible, might serve as a good platform for future development. It's obvious that FlightGear, as every visual simulation, has to depend on the viewer. But the opposite way of depending the viewer part heavily on core FlightGear components is certainly not going into the outlined direction.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23055.html |title=[Flightgear-devel] fgviewer|author=Martin Spott |date=11 Aug 2009}}</ref>}} | |||
{{cquote|I also think it's a good idea to factor out the dependencies that the visual part of flightgear has on the whole flightgear implementation. It's not right at the head of my queue, but I support the idea and will look for ways to move it along.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23067.html |title=[Flightgear-devel] fgviewer|author=Tim Moore |date=11 Aug 2009}}</ref>}} | |||
{{cquote|Currently I for myself am more working on pulling out different components from the simulation. As a side effect I am doing that work on fgviewer which should do a standalone viewer component. I cannot recommend to use fgviewer for anything today because plenty of stuff is missing. But that was the place that I thought would be a good start to implement this kind of doing | |||
fog/atmospheric scattering.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23067.html |title=[Flightgear-devel] Earthview - Orbital terrain rendering in FG|author=Mathias Fröhlich |date=Mon, 19 Mar 2012}}</ref>}} | |||
<references/> | |||
== Background == | == Background == | ||