20,741
edits
QtQuick use in FlightGear: Difference between revisions
Jump to navigation
Jump to search
→Background
| Line 4: | Line 4: | ||
== Background == | == Background == | ||
In January 2015, James Turner began prototyping (at the suggestion / encouragement of Curt, Torsten D & others) a GUI integration for FlightGear based on Qt 5.<ref>{{cite web | In January 2015, James Turner began prototyping (at the suggestion / encouragement of Curt, Torsten D & others) a GUI integration for FlightGear based on Qt 5. | ||
The goal is to make an *optional* Qt dependency to replace PLIB PUI. Except of course PUI will have to remain for some awkward use cases in the short term (aircraft dialogs, potentially).<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/33245028/ | |url = https://sourceforge.net/p/flightgear/mailman/message/33245028/ | ||
|title = <nowiki> [Flightgear-devel] Gui technologies </nowiki> | |title = <nowiki> [Flightgear-devel] Gui technologies </nowiki> | ||
| Line 12: | Line 13: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
There's been a strong division of opinion among a couple of core developers with respect to the question whether a QT dependency is desirable or not. In one of the hangouts in 2015, we had the chance to discuss the pros and cons, when the most outspoken developers regarding this issue were both present. | There's been a strong division of opinion among a couple of core developers with respect to the question whether a QT dependency is desirable or not. In one of the hangouts in 2015, we had the chance to discuss the pros and cons, when the most outspoken developers regarding this issue were both present. | ||