FlightGear Qt launcher

From FlightGear wiki
Revision as of 20:56, 8 March 2015 by Hooray (talk | contribs) (needs de-quoting & cleanup still)
Jump to navigation Jump to search
This article is a stub. You can help the wiki by expanding it.

Background

Cquote1.png the launcher is not run by default :)


This is because it was created as a Mac only solution. We need to have the discussion if it should become the default launcher for Windows (Linux and other Unixes are less relevant, it’s up to the distribution packagers).

You can test the launcher by passing the ‘—launcher’ argument, or setting the FG_LAUNCHER env var. These options exist to allow a Windows shortcut, .desktop file on Linux or the app bundle’s Info.plist to set the value when started from the GUI.

And if you run fgfs via the command line with some options, you don’t get troubled by the launcher - the idea being to minimise how much of my life I spend being shouted at by the Internet. Which is already way more than I would like.

Note the launcher on ‘next’ will be in flux shortly as I add some new features - support for the aircraft package manager especially, and for specifying some directory locations to support ‘code only’ nightly builds which use an existing FGData download.


Cquote2.png

Status

Cquote1.png Related to Qt, I can say that up to now - as far as I can tell - only a simple replacement for the Mac Launcher has been introduced. This is not related to the internal user interface of FlightGear, at least for now. If, how and when the internal gui can leverage Qt is under investigation and in such an early state that those responsible preferred to not announce anything yet. If this ever happens, this will be discussed on the mailing list
Cquote2.png

Dependencies

Cquote1.png Qt is only needed for the launcher feature, which is automatically disabled if it is not found.
Cquote2.png
Cquote1.png If CMake does not find QT5 then it skips the QT launcher compilation
Cquote2.png

Variants

Cquote1.png I had a problem with the Qt-launcher for Mac, that we have no way to identify the ‘main’ variant of an aircraft, which can cause confusing UI for new users. Going forwards I’d like a -set.xml tag to identify the main variant, this would help the aircraft packaging logic, unless anyone has a better solution?
Cquote2.png