FlightGear Qt launcher: Difference between revisions

Jump to navigation Jump to search
m
→‎FGRun: (forum2wiki) still needs de-quoting
m (→‎FGRun: (forum2wiki) still needs de-quoting)
Line 94: Line 94:


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>http://sourceforge.net/p/flightgear/codetickets/1591/#4cb7</ref>.
{{DeQuote}}
{{FGCquote
  |FGRun will be replaced by the built-in launcher in the next weeks, this is a known long term goal that's why FGRun haven't been improved the last 6 months and he won't be improved anymore. By using FGRun you won't be able to use all the new features in the future.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=235136#p235136
    |title=<nowiki>Re: FGRUN I think it's useful add it in a standard way</nowiki>
    |author=<nowiki>F-JJTH</nowiki>
    |date=<nowiki>Sat Mar 14</nowiki>
  }}
}}
{{FGCquote
  |it isn't just a rewrite from scratch... it is built into fgfs... not a separate executable... i suspect that when it is completed, "--launcher" will be removed and it will be the first thing you see when starting fgfs but i could be wrong about that
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=235178#p235178
    |title=<nowiki>Re: FGRUN I think it's useful add it in a standard way</nowiki>
    |author=<nowiki>wkitty42</nowiki>
    |date=<nowiki>Sat Mar 14</nowiki>
  }}
}}
{{FGCquote
  |fgfs has to at least be built with Qt5... on my linux system, i don't recall any Qt5 stuff being installed when i first pulled fgfs 3.4.0 from the PPA where they (sorry, i don't recall his name as i'm still very new and learning everyone) had built 3.4.0 and then 3.4.1 with Qt5... when i started using the download_and_compile script, Qt5 was not installed on my machine so the --launcher option didnt work with my self-compiled 3.5.0... then some updates were made and i got a new copy of the script because of the fgdata split and that did install some Qt5 stuff on my box... i'm guessing that the installers will take care of what needs to be
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=235217#p235217
    |title=<nowiki>Re: FGRUN I think it's useful add it in a standard way</nowiki>
    |author=<nowiki>wkitty42</nowiki>
    |date=<nowiki>Sun Mar 15</nowiki>
  }}
}}
{{FGCquote
  |3.4 will need, if you have system-side QT5 libraries, namely the qtbase5-dev package on Ubuntu that provides these QT libraries.<br/>
<br/>
i still think FGRUN is ment to stay,,,<br/>
<br/>
edit: at least if you compile stable FG from the brisa's download_and_compile script, you'll need QT, but it might still error compile even if your compiling by hand... but there's an QT conditional commit on Sourceforge's "next" for those without QT, but i'm not sure if it's merged yet into release/3.4
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=235630#p235630
    |title=<nowiki>Re: FGRUN I think it's useful add it in a standard way</nowiki>
    |author=<nowiki>hamzaalloush</nowiki>
    |date=<nowiki>Tue Mar 17</nowiki>
  }}
}}
{{FGCquote
  |grun is a separate tool, so can obviously be used just as well - and it is very likely that it will be much more complete than the Qt based launcher for at least 2-3 release cycles, which also applies to other polished front-ends, like for example FGx.<br/>
<br/>
However, the mid-term idea is to phase out external launchers and provide built-in means to start up and configure FG using a simple UI.<br/>
Also, for the last few years, Gijs  has basically been maintaining fgrun - and here's what he had to say about the future of fgrun in fgfs: [http://sourceforge.net/p/flightgear/codetickets/1529/#cd07 http://sourceforge.net/p/flightgear/cod ... 1529/#cd07]
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=235634#p235634
    |title=<nowiki>Re: FGRUN I think it's useful add it in a standard way</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Tue Mar 17</nowiki>
  }}
}}
{{FGCquote
  |The other issue here being that the Qt launcher in its current form is implemented in a way that makes it only useful during startup, i.e. the current implementation basically kills the UI once the simulator has initialized. So it's not just a certain disparity features-wise, but the UI also won't be available at run-time, which may take another 1-2 release cycles to address.<br/>
<br/>
Obviously, people can continue to use external launchers like fgrun/fgx still - but there are pretty strong advantages once a built-in launcher is properly integrated - so if/when, the Qt5-based UI will evolve, it is likely that external launchers will generally become obsolete for most purposes/end-users - which isn't such a bad thing actually, given the crazy number of FG GUI front-ends we have seen over the years.<br/>
<br/>
Keep in mind that an external launcher like fgrun will also eat up resources while FG is running - while an integrated solution could be much more efficient.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=235634#p235634
    |title=<nowiki>Re: FGRUN I think it's useful add it in a standard way</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Tue Mar 17</nowiki>
  }}
}}
{{FGCquote
  |i applaud this effort by Gijs, but i still think users should be able to use external tools as well, as you have confirmed now thankfully.<br/>
<br/>
since QT is bieng agreed upon to be the launcher for FG accross platforms, does this mean it will merge into FG as well?? i think Canvas is much better for menu since we are using built-in framework.<br/>
<br/>
not to mention other QT dependance and maintanance issues.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=235635#p235635
    |title=<nowiki>Re: FGRUN I think it's useful add it in a standard way</nowiki>
    |author=<nowiki>hamzaalloush</nowiki>
    |date=<nowiki>Tue Mar 17</nowiki>
  }}
}}
{{FGCquote
  | the whole step is long overdue - and for FG it is a huge improvement. FlightGear has become a fairly sizable code base, with tons of legacy code, while making very little use of modern frameworks/libraries. Accepting Qt5 as a general dependency would be a huge shift in thinking, and it could help improve/modernize the FG architecture significantly.<br/>
However, it's a tedious process, too - i.e. updating all the legacy code accordingly and getting rid of old cruft in the process.<br/>
And so far, there's only a single core developer pursuing this. And looking back in time, we've seen similar efforts that ultimately turned out to be too tedious to be accepted by the wider communtiy of contributors, so that such efforts would ultimately turn out to be merely "experiments" - and "iterations" of a process to arrive at a completely different solution.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=235646#p235646
    |title=<nowiki>Re: FGRUN I think it's useful add it in a standard way</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Tue Mar 17</nowiki>
  }}
}}
{{FGCquote
  |having started without any kind of launcher and then finding FGRun and now having played with the Qt5 launcher, i do hope that all the capabilities of FGRun are incorporated into the new one... i'm always getting bitten in the arse when i forget to specify something on the command line with the "--launcher" option... "--http{{=}}5500" being one of those... there are others... FGRun saves the last used options so the next time they are already set...
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=235167#p235167
    |title=<nowiki>Re: FGRUN I think it's useful add it in a standard way</nowiki>
    |author=<nowiki>wkitty42</nowiki>
    |date=<nowiki>Sat Mar 14</nowiki>
  }}
}}


== Testing ==
== Testing ==

Navigation menu