FFGo: Difference between revisions

Jump to navigation Jump to search
872 bytes added ,  25 November 2019
→‎Using pip (generic method): No need to add a separate anchor to link to a section. Use <Article>"#"<Section>, like FFGo#Using pip (generic method) instead
(Update for release 1.11.3 and new home page (proof: OpenPGP-signed tarballs and zip files at http://frougon.net/projects/FFGo/dist/ and https://pypi.python.org/pypi/FFGo))
(→‎Using pip (generic method): No need to add a separate anchor to link to a section. Use <Article>"#"<Section>, like FFGo#Using pip (generic method) instead)
(16 intermediate revisions by 3 users not shown)
Line 3: Line 3:
| title                  = FFGo
| title                  = FFGo
| image                  = FFGo LPMA-apt-tooltip-and-FG-cmd.png
| image                  = FFGo LPMA-apt-tooltip-and-FG-cmd.png
| alt                    = Screenshot of FFGo 1.10.1
| alt                    = Screenshot of FFGo 1.12.3
| developedby            = Florent Rougon
| developedby            = Florent Rougon
| type                  = Graphical launcher for FlightGear
| type                  = Graphical launcher for FlightGear
| initialrelease        = 1.0.0 (Aug 21, 2015)
| initialrelease        = 1.0.0 (Aug 21, 2015)
| latestrelease          = 1.11.3 (Apr 30, 2016)
| latestrelease          = 1.12.5 (March 29, 2017)
| writtenin              = Python 3
<!-- simplifying Python3 to Python for the category to work correctly-->
| writtenin              = Python
| writteninversion              = 3
| os                    = Unix-like (incl. Linux), Windows, MacOS X
| os                    = Unix-like (incl. Linux), Windows, MacOS X
| developmentstatus      = Active (as of April 2016)
| developmentstatus      = Active (as of March 2017)
| website                = http://frougon.net/projects/FFGo/
| website                = http://frougon.net/projects/FFGo/
| license                = {{wikipedia|WTFPL#Version 2|WTFPL version 2|noicon=1}}
| license                = {{wikipedia|WTFPL#Version 2|WTFPL version 2|noicon=1}}
Line 38: Line 40:
* easy viewing and saving of FlightGear output (log);
* easy viewing and saving of FlightGear output (log);
* automatic FFGo + FlightGear log saving and rotating;
* automatic FFGo + FlightGear log saving and rotating;
* ability to read and merge an arbitrary number of in-scenery-paths, uncompressed or gzip-compressed apt.dat files. This is compliant with a feature<ref name="multi-apt.dat-input">In short, FlightGear and FFGo now read and merge all <tt>$scenery_path/NavData/apt/*.dat[.gz]</tt> files for each scenery path, plus the default <tt>$FG_ROOT/Airports/apt.dat.gz</tt>, coming last.</ref> [https://sourceforge.net/p/flightgear/flightgear/ci/516a5cf016a7d504b09aaac2e0e66c7e9efd42b2/ introduced in FlightGear 2016.4.0], more precisely on October 17, 2016. For the interfacing with FFGo, FlightGear must be more recent than November 9, 2016 (precisely, [https://sourceforge.net/p/flightgear/flightgear/ci/fb10f76e59ef0fbe598befb895daaf2969b78e0c/ FlightGear commit fb10f76e] is needed). FlightGear 2016.3.x and older still work with FFGo, but using the old behavior, where only <tt>$FG_ROOT/Airports/apt.dat.gz</tt> is read.
* complete German translation, complete French translation except for the help file ([https://github.com/frougon/FFGo/blob/master/ffgo/data/help/help_en en], [https://github.com/frougon/FFGo/blob/master/ffgo/data/help/help_fr fr]), other translations currently outdated (English is the language FFGo is written in, thus it is obviously complete, and not a translation ''per se'').
* complete German translation, complete French translation except for the help file ([https://github.com/frougon/FFGo/blob/master/ffgo/data/help/help_en en], [https://github.com/frougon/FFGo/blob/master/ffgo/data/help/help_fr fr]), other translations currently outdated (English is the language FFGo is written in, thus it is obviously complete, and not a translation ''per se'').


Line 498: Line 501:
command—using digital signatures, done with each participant's key).
command—using digital signatures, done with each participant's key).
</li>
</li>
<li>Then, in order to have they key in a separate file, say <tt>~/tmp/flo-key</tt>, you can run:
<li>Then, in order to have the key in a separate file, say <tt>~/tmp/flo-key</tt>, you can run:


<syntaxhighlight lang="shell" enclose="div">
<syntaxhighlight lang="shell" enclose="div">
Line 535: Line 538:
deb-src http://frougon.net/debian-ffgo unstable main</pre>
deb-src http://frougon.net/debian-ffgo unstable main</pre>


<p>(replace <tt>unstable</tt> with <tt>jessie</tt> if you are using <i>jessie</i>)</p>
<p>(replace <i>unstable</i> with <i>stretch</i> if you are using Debian 9, also known as <i>stretch</i>)</p>
</li>
</li>
<li>'''Third step: update the <tt>apt</tt> package list'''
<li>'''Third step: update the <tt>apt</tt> package list'''
Line 557: Line 560:
<li><tt>python3-geographiclib</tt> if available for your distribution (i.e., after <i>jessie</i>), for better geodesic calculations.</li></ul>
<li><tt>python3-geographiclib</tt> if available for your distribution (i.e., after <i>jessie</i>), for better geodesic calculations.</li></ul>


<p>In other words, if you are using ''unstable'', you can run:</p>
<p>In other words, if you are using Debian ''stretch'' or later, you can run:</p>


<pre>apt-get install ffgo python3-pil.imagetk geographiclib-tools python3-geographiclib</pre>
<pre>apt-get install ffgo python3-pil.imagetk geographiclib-tools python3-geographiclib</pre>
Line 564: Line 567:


<pre>apt-get install ffgo python3-pil.imagetk geographiclib-tools</pre>
<pre>apt-get install ffgo python3-pil.imagetk geographiclib-tools</pre>
{{Note|To avoid pulling in the entire FlightGear packages, you could tell apt-get to not install the recommendations in the deb file:<br>
<code>apt-get install --no-install-recommends ffgo python3-pil.imagetk geographiclib-tools python3-geographiclib</code><br>
This is useful, if you have FG installed some other way, than by your package manager.}}


{{Note|Installing the <tt>geographiclib-tools</tt> package is not enough to have the <tt>MagneticField</tt> program working. This program needs one or more datasets which are not part of the <tt>geographiclib-tools</tt> package. One easy way to install the minimal dataset on Debian is to run the following command with root privileges:
{{Note|Installing the <tt>geographiclib-tools</tt> package is not enough to have the <tt>MagneticField</tt> program working. This program needs one or more datasets which are not part of the <tt>geographiclib-tools</tt> package. One easy way to install the minimal dataset on Debian is to run the following command with root privileges:
Line 623: Line 630:
Just as for the [https://pip.pypa.io/ pip] command explained above, think of <code>/usr/bin/python3.4 -m venv</code> as the name of a program (it just runs the main function of the Python <tt>venv</tt> module). In the above command, you can freely choose the <venv-dir> directory. It is just a directory that is going to contain the newly-created virtual environment once this command returns (therefore, you shouldn't have anything inside it before running the command, otherwise that would be messy).
Just as for the [https://pip.pypa.io/ pip] command explained above, think of <code>/usr/bin/python3.4 -m venv</code> as the name of a program (it just runs the main function of the Python <tt>venv</tt> module). In the above command, you can freely choose the <venv-dir> directory. It is just a directory that is going to contain the newly-created virtual environment once this command returns (therefore, you shouldn't have anything inside it before running the command, otherwise that would be messy).


<p>Notes:</p>
<p>Note:</p>
<blockquote>
<blockquote>
<ul><li><p>Some systems may provide executables named <tt>pyvenv-3.4</tt> or similar. For instance, on Debian, <tt>/usr/bin/pyvenv-3.4</tt> is a “shortcut” for <code>/usr/bin/python3.4 -m venv</code>. Thus, one may type:</p>
<p>Some systems may provide executables named <tt>pyvenv-3.4</tt> or similar. For instance, on Debian, <tt>/usr/bin/pyvenv-3.4</tt> is a “shortcut” for <code>/usr/bin/python3.4 -m venv</code>. Thus, one may type:</p>


<syntaxhighlight lang="shell" enclose="div">
<syntaxhighlight lang="shell" enclose="div">
Line 632: Line 639:


<p>to obtain the same effect as above: creating a virtual environment in <venv-dir> based on the Python interpreter <tt>/usr/bin/python3.4</tt>. Thanks to shell command history, using <code>/usr/bin/python3.4 -m venv</code> is not much of a problem, and since this makes it quite clear which Python interpreter is going to be used, I'll favor this syntax here rather than the shorter syntax based on <tt>pyvenv-3.4</tt>.</p>
<p>to obtain the same effect as above: creating a virtual environment in <venv-dir> based on the Python interpreter <tt>/usr/bin/python3.4</tt>. Thanks to shell command history, using <code>/usr/bin/python3.4 -m venv</code> is not much of a problem, and since this makes it quite clear which Python interpreter is going to be used, I'll favor this syntax here rather than the shorter syntax based on <tt>pyvenv-3.4</tt>.</p>
</li>
<li>
  <p>
    If you use Debian <i>unstable</i>, be sure to have the <tt>python3.5*</tt>
    packages in version 3.5.1-8 or newer (these were uploaded on March 18,
    2016). With earlier versions, creating a virtual environment
    [https://bugs.debian.org/815864 could fail]. Workarounds have been given in
    [http://forum.flightgear.org/viewtopic.php?f=18&t=27054&p=278031#p278031 this message on the FlightGear forum],
    but the simplest thing to do now is to just make sure that your
    <tt>python3.5*</tt> packages are recent enough.
  </p>
</li>
</ul>
</blockquote>
</blockquote>


Line 1,121: Line 1,115:


[[Category:FlightGear front ends]]
[[Category:FlightGear front ends]]
<!--
[[Category:Python Software]]
-->

Navigation menu