FlightGear Qt launcher: Difference between revisions

Jump to navigation Jump to search
m
→‎Background: while getting rid of PUI is a declared goal, making Qt5 mandatory is not ...
(Add background and re-order some things)
m (→‎Background: while getting rid of PUI is a declared goal, making Qt5 mandatory is not ...)
Line 36: Line 36:


== Background ==
== Background ==
{{Disputed}}
In accordance with the [[FlightGear 4.xx Roadmap]], FlightGear's current GUI interface, based on the [[PUI]] library of [[PLIB]], will be replaced by one based on Qt. [[FGRun]] will also be removed in future to be replaced by this launcher. In addition, a brower-based UI (called [[Phi]]) will continue to be developed in parallel. This will result in the following user interface:
In accordance with the [[FlightGear 4.xx Roadmap]], FlightGear's current GUI interface, based on the [[PUI]] library of [[PLIB]], will be replaced by one based on Qt. [[FGRun]] will also be removed in future to be replaced by this launcher. In addition, a brower-based UI (called [[Phi]]) will continue to be developed in parallel. This will result in the following user interface:
* Qt launcher
* Qt launcher
Line 41: Line 42:
* External browser-based UI (Phi)
* External browser-based UI (Phi)


As of April 2016, the Qt launcher is run inside the simulator itself, unlike FGRun, which is a separate program. Eventually, the Qt launcher will be split away into separate program and fully replace FGRun.
As of April 2016, the Qt launcher is integrated in the fgfs binary itself, and run prior to the simulator, unlike FGRun, which is a separate program. Eventually, the Qt launcher will be split away into separate program and fully replace FGRun.


== Status ==
== Status ==

Navigation menu