20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
→Background
m (→History and status: https://sourceforge.net/p/flightgear/mailman/message/35689137/) |
|||
| Line 78: | Line 78: | ||
}}</ref> This will result in the following user interface: | }}</ref> This will result in the following user interface: | ||
* Qt launcher | * Qt launcher | ||
* Internal UI based | * Internal UI based possibly with Qt/[[Canvas]] integration | ||
* External browser-based UI (Phi) | * External browser-based UI (Phi) | ||
| Line 87: | Line 87: | ||
|date = Oct 11th, 2015 | |date = Oct 11th, 2015 | ||
}}</ref> | }}</ref> | ||
As of 05/2017, James is still very much undecided about which technology to use for in-sim GUI, he is somewhat inclined towards using the Canvas, because it avoids some rendering issues (but exposes a few more, + some performance ones) but the problem is James is fairly unhappy with the GUI / widget API in the Canvas right now - it does not satisfy his ideas about how simple + robust such an API should be, James needs to evaluate if the current API can be improved or needs to be drastically changed. The other issue is to use QtQuick rendered into OpenGL, which has a very nice robust and well-designed API, but adds some dependencies and complicates the rendering architecture, which makes him nervous about multi-window setups and other more esoteric OSG configs.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35863607/ | |||
|title = <nowiki> Re: [Flightgear-devel] KBOS runway list? are there 10 or are there | |||
12? </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = May 28th, 2017 | |||
|added = May 28th, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
== Usage == | == Usage == | ||