20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 49: | Line 49: | ||
For the time being, Qt is only needed for the launcher feature, which is automatically disabled if it is not found<ref>http://sourceforge.net/p/flightgear/mailman/message/33498614/</ref>. | For the time being, Qt is only needed for the launcher feature, which is automatically disabled if it is not found<ref>http://sourceforge.net/p/flightgear/mailman/message/33498614/</ref>. | ||
If CMake does not find QT5 then it skips the QT launcher compilation<ref>http://sourceforge.net/p/flightgear/mailman/message/33498869/</ref>. Thus, Qt5 is an optional build dependency and people can continue to other other front-ends. | If CMake does not find QT5 then it skips the QT launcher compilation<ref>http://sourceforge.net/p/flightgear/mailman/message/33498869/</ref>. Thus, Qt5 is an optional build dependency and people can continue to other other front-ends. | ||
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). | |||
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<ref>http://forum.flightgear.org/viewtopic.php?p=229563#p229563</ref> | |||
=== Canvas === | === Canvas === | ||
| Line 62: | Line 66: | ||
For now, 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). 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). | For now, 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). 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). | ||
Related to Qt, up to now - 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 | Related to Qt, up to now - 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<ref>http://forum.flightgear.org/viewtopic.php?p=229563#p229563</ref>. | ||
=== FGRun === | === FGRun === | ||
| Line 70: | Line 74: | ||
== Testing == | == Testing == | ||
The launcher is not run by default, this is because it was created as a Mac only solution | The launcher is not run by default, this is because it was created as a Mac only solution. | ||
You can test the launcher by passing the <code>--launcher</code> argument, or setting the <code>$FG_LAUNCHER</code> environment variable. 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. | You can test the launcher by passing the <code>--launcher</code> argument, or setting the <code>$FG_LAUNCHER</code> environment variable. 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. | ||