FlightGear Qt launcher: Difference between revisions

Jump to navigation Jump to search

FlightGear Qt launcher (view source)

Revision as of 20:59, 30 April 2016

751 bytes added ,  30 April 2016
More ref expansion
(Start doing full references (as opposed to just URLs). Also combine duplicates)
(More ref expansion)
Line 214: Line 214:
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 name="GUIhell"/>.
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 name="GUIhell"/>.


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>.  
However, the goal is to make an '''optional''' Qt dependency to replace PLIB PUI<ref>{{cite web
|url    = http://sourceforge.net/blog/november-2015-community-choice-project-of-the-month-flightgear/
|title  = November 2015, "Community Choice" Project of the Month – FlightGear
|author = SourceForge Community Team
|date  = Nov 1st, 2015
}}</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).
Line 260: Line 265:


=== FGRun ===
=== FGRun ===
The upcoming FlightGear 3.6 release is likely to contain an integrated, hard-coded, launcher based on Qt5 to work around the issue of the mac launcher no longer working on Yosemite<ref>http://forum.flightgear.org/viewtopic.php?p=228961#p228961</ref>, because James Turner is prototyping a Qt5 cross-platform GUI <ref>http://forum.flightgear.org/viewtopic.php?p=232593#p232593</ref>.
The upcoming FlightGear 3.6 release is likely to contain an integrated, hard-coded, launcher based on Qt5 to work around the issue of the mac launcher no longer working on Yosemite<ref>{{cite web
|url    = http://forum.flightgear.org/viewtopic.php?p=228961#p228961
|title  = Re: FG cannot be opened on new iMac
|author = Hooray
|date  = Jan 4th, 2015
}}</ref>, because James Turner is prototyping a Qt5 cross-platform GUI <ref>{{cite web
|url    = http://forum.flightgear.org/viewtopic.php?p=232593#p232593
|title  = Re: Request for a modernized FGRUN
|author = elgaton
|date  = Feb 20th, 2015
}}</ref>.


Once we have a built-in Qt launcher that's shipped by default on Mac it will probably be used on other OS in the coming release. FGRun will be gone by then, FGRun will be gone with the next release of FlightGear, in favour of a built-in launcher.<ref>http://sourceforge.net/p/flightgear/codetickets/1591/#4cb7</ref>.
Once we have a built-in Qt launcher that's shipped by default on Mac it will probably be used on other OS in the coming release. FGRun will be gone by then, FGRun will be gone with the next release of FlightGear, in favour of a built-in launcher.<ref>{{cite web
|url    = http://sourceforge.net/p/flightgear/codetickets/1591/#4cb7
|title  = Re: #1591 Restore defaults sets invalid paths
|author = Gijs de Rooy
|date  = Mar 8th, 2015
}}</ref>.


{{DeQuote}}
{{DeQuote}}
Line 416: Line 436:
== Testing ==
== Testing ==
Any version of Qt newer than 5.1 works - we need to keep it backwards compatible and of course Qt is forwards compatible.
Any version of Qt newer than 5.1 works - we need to keep it backwards compatible and of course Qt is forwards compatible.
<ref> {{cite web
<ref>{{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/35020030/
|url    = http://sourceforge.net/p/flightgear/mailman/message/35020030/
  | title  = <nowiki>Re: [Flightgear-devel] MSVC 2012 or 2013 support?</nowiki>
|title  = <nowiki>Re: [Flightgear-devel] MSVC 2012 or 2013 support?</nowiki>
  | author = <nowiki>James Turner</nowiki>
|author = James Turner
  | date  = Apr 17th, 2016
|date  = Apr 17th, 2016
  | added  = Apr 17th, 2016
}}</ref>
  | script_version = 0.26
  }}
</ref>


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.  
Line 448: Line 465:
}}
}}


The GUI launcher included in the [[FlightGear Build Server|nightly builds]] includes a new dialog to set up (and remember) [[$FG_ROOT]] using a file picker dialog. It does some version checking to hopefully make things as robust as possible for the user<ref>http://sourceforge.net/p/flightgear/mailman/message/33646906/</ref>.
The GUI launcher included in the [[FlightGear Build Server|nightly builds]] includes a new dialog to set up (and remember) [[$FG_ROOT]] using a file picker dialog. It does some version checking to hopefully make things as robust as possible for the user<ref>{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33646906/
|title  = <nowiki>Re: [Flightgear-devel] Download description page</nowiki>
|author = James Turner
|date  = Mar 26th, 2015
}}</ref>.


And if you run fgfs via the command line with some options, you don’t get troubled by the launcher.
And if you run fgfs via the command line with some options, you don’t get troubled by the launcher.
Line 483: Line 505:


== Development ==
== Development ==
Note the launcher on '''next''' will be in flux shortly as James will add some new features - support for the [[FlightGear Package Manager|aircraft package manager]] especially, and for specifying some directory locations to support "code only" nightly builds (see [[FlightGear Build Server]]) which use an existing FGData download<ref>http://sourceforge.net/p/flightgear/mailman/message/33503142/</ref>.
Note the launcher on '''next''' will be in flux shortly as James will add some new features - support for the [[FlightGear Package Manager|aircraft package manager]] especially, and for specifying some directory locations to support "code only" nightly builds (see [[FlightGear Build Server]]) which use an existing FGData download<ref>{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33503142/
|title  = <nowiki>Re: [Flightgear-devel] Qt launcher requirement bump in Flightgear git</nowiki>
|author = James Turner
|date  = Feb 27th, 2015
}}</ref>.


{{FGCquote
{{FGCquote
Line 509: Line 536:


* [http://forum.flightgear.org/viewtopic.php?f=22&t=26504#p246868 Airplane is in FG root, can't see in flightgear wizard]
* [http://forum.flightgear.org/viewtopic.php?f=22&t=26504#p246868 Airplane is in FG root, can't see in flightgear wizard]
* {{bug|1772}}
* {{ticket|1772|bug}}


{{FGCquote
{{FGCquote
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/97589"

Navigation menu