FlightGear Qt launcher: Difference between revisions

Jump to navigation Jump to search
m
Line 124: Line 124:
=== PLIB/PUI (legacy GUI) ===
=== PLIB/PUI (legacy GUI) ===
{{Main article|Howto:Processing legacy PUI dialogs using Canvas}}
{{Main article|Howto:Processing legacy PUI dialogs using Canvas}}
Up to now - only a simple replacement for the Mac Launcher has been introduced (and enabled by default only on OSX). This is not related to the internal user interface of FlightGear (which is mainly based on PUI and increasingly Canvas these days), at least for now<ref>http://forum.flightgear.org/viewtopic.php?p=229563#p229563</ref>.
Up to now - only a simple replacement for the Mac Launcher has been introduced (and enabled by default only on OSX). This is not related to the internal user interface of FlightGear (which is mainly based on [[PUI]] and increasingly Canvas these days), at least for now<ref>http://forum.flightgear.org/viewtopic.php?p=229563#p229563</ref>.


However, the goal is to make an '''optional''' Qt dependency to replace PLIB PUI.  
However, the goal is to make an '''optional''' Qt dependency to replace PLIB PUI<ref>http://sourceforge.net/blog/november-2015-community-choice-project-of-the-month-flightgear/</ref>.  


Except of course PUI will have to remain for some awkward use cases in the short term (aircraft dialogs, potentially). When compiled without Qt support, you’ll get a fully functional FG (i.e., '''Qt will never be a requirement to build FG'''), but without the GUI functions – which is indeed what some people want anyway (e.g., in some home cockpit setups).
Except of course PUI will have to remain for some awkward use cases in the short term (aircraft dialogs, potentially). When compiled without Qt support, you’ll get a fully functional FG (i.e., '''Qt will never be a requirement to build FG'''), but without the GUI functions – which is indeed what some people want anyway (e.g., in some home cockpit setups).

Navigation menu