FlightGear wiki - User contributions [en]

Howto:Install aircraft

2016-04-18T15:09:59Z

Jaxsin: updated with Git info for renaming the folder so FG will work as expected

{{installing}}

The latest official [[aircraft]] can be downloaded at [http://www.flightgear.org/download/ FlightGear.org Aircraft], which then usually require unzipping software to extract from a compressed file format. Then these must be manually installed in a FlightGear software installation to use. The details depend on the method of download, operating system, and user setup. Alternatively if you are using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], or you wish to manage your aircraft collection using version control tools, the aircraft can be obtained directly from the [[FGAddon|official FlightGear aircraft repository - FGAddon]].

== Installation process ==
=== Linux ===
(Ubuntu 12.04)
# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside <tt>/usr/share/games/flightgear/</tt>. For example, use <tt>/home/{YourUserName}/FlightGear/Aircraft</tt>.
# Extract your aircraft file into the folder (the one you created above)
#: unzip XXXXX.zip
# Start up FlightGear. Append the root aircraft folder (<tt>/home/{YourUserName}/FlightGear/Aircraft</tt> in our example) to the $FG_AIRCRAFT list on the first page (previous to aircraft selection) of the launcher. Your aircraft should now show up in the list.

=== Macintosh OS X ===
{{out of date}}

# Open GUI Launcher for FlightGear Mac
# Click on "Others" tab at middle right of launcher
# Click "Install Add-On Data" link at bottom of launcher
# Select aircraft folder from menu, and click "Open"
# Click OK on pop-up box.

Please note: For Mac users, the above will not work if you have not installed FG to the applications folder. If you do not want to put your version of FG in your applications folder, you can place it in a separate folder of your own creation. That will allow the above aircraft (& scenery) installation method to work correctly/

=== Windows ===
# Download an aircraft and save it on your desktop.
# Unzip the file using a file archiver, for example the open source file archiver [http://www.7-zip.org/ 7-Zip].
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory. For example, use <tt>C:\Users\{YourUserName}\Documents\FlightGear\Aircraft</tt>.
# Move the unzipped folder (usually the aircraft's name) to your that aircraft directory.
# Start up FlightGear. Append the root aircraft folder (<tt>C:\Users\{YourUserName}\Documents\FlightGear\Aircraft</tt> in our example) to the <tt>[[$FG_AIRCRAFT]]</tt> list on the first page (previous to aircraft selection) of the launcher. Your aircraft should now show up in the list.

== When installing an aircraft fails ==
=== XML files with wrong encoding ===
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.

To fix this on Linux try this:

$ cd path/to/aircraft/directory/
$ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'

=== Rename Aircraft Folder ===
If you start FlightGear with the aircraft you installed it is invisible or if FlightGear will not start with your newly installed aircraft, but will start with other aircraft you might need to rename the aircraft folder.

If there is a readme file have a look there for instructions, otherwise try change to more obvious names like renaming for example "A320-master" to "A320" or "boeing-707" to "707". If that does not work ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the [http://forum.flightgear.org/viewforum.php?f=11 forum].

==== Installing From Git Repo ====
If you have downloaded a *.zip file of an aircraft from github or other online repository you must rename the extracted folder name and remove the -[branch] tag. The folder name must correspond to the [/b]<aircraft>[/b]-set.xml file contained inside of the extracted folder. This is something that git automatically does when you download a zip file. The better way would be to learn and use git

$ git clone http://repo.address/here.git

== Choosing aircraft ==
If you are looking for information to decide what aircraft to download, try:
* [[Aircraft]]
* [[Helicopter]]
* [[Vehicle]]
* [[Table of models]]
External links to third party aircraft can be found at [[FlightGear hangars]]. Remember that the latest aircraft may not load with previous versions. If you happen to use an older version of FlightGear, look for older aircraft in the links section.

== For developers ==
Help develop the [[FlightGear Package Manager]] which is intended to support automatic aircraft and scenery installation, currently in alpha development and in need of testing.

== Related content ==
* [[Installing Scenery]]

[[Category:Howto|Install aircraft]]

[[de:Howto:Flugzeuge Installieren]]
[[es:Cómo:Instalar_aviones]]
[[fr:Howto Installer un avion]]

Howto:Install aircraft

2016-04-18T15:04:22Z

Jaxsin: /* The aircraft folder have to be renamed */

{{installing}}

The latest official [[aircraft]] can be downloaded at [http://www.flightgear.org/download/ FlightGear.org Aircraft], which then usually require unzipping software to extract from a compressed file format. Then these must be manually installed in a FlightGear software installation to use. The details depend on the method of download, operating system, and user setup. Alternatively if you are using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], or you wish to manage your aircraft collection using version control tools, the aircraft can be obtained directly from the [[FGAddon|official FlightGear aircraft repository - FGAddon]].

== Installation process ==
=== Linux ===
(Ubuntu 12.04)
# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside <tt>/usr/share/games/flightgear/</tt>. For example, use <tt>/home/{YourUserName}/FlightGear/Aircraft</tt>.
# Extract your aircraft file into the folder (the one you created above)
#: unzip XXXXX.zip
# Start up FlightGear. Append the root aircraft folder (<tt>/home/{YourUserName}/FlightGear/Aircraft</tt> in our example) to the $FG_AIRCRAFT list on the first page (previous to aircraft selection) of the launcher. Your aircraft should now show up in the list.

=== Macintosh OS X ===
{{out of date}}

# Open GUI Launcher for FlightGear Mac
# Click on "Others" tab at middle right of launcher
# Click "Install Add-On Data" link at bottom of launcher
# Select aircraft folder from menu, and click "Open"
# Click OK on pop-up box.

Please note: For Mac users, the above will not work if you have not installed FG to the applications folder. If you do not want to put your version of FG in your applications folder, you can place it in a separate folder of your own creation. That will allow the above aircraft (& scenery) installation method to work correctly/

=== Windows ===
# Download an aircraft and save it on your desktop.
# Unzip the file using a file archiver, for example the open source file archiver [http://www.7-zip.org/ 7-Zip].
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory. For example, use <tt>C:\Users\{YourUserName}\Documents\FlightGear\Aircraft</tt>.
# Move the unzipped folder (usually the aircraft's name) to your that aircraft directory.
# Start up FlightGear. Append the root aircraft folder (<tt>C:\Users\{YourUserName}\Documents\FlightGear\Aircraft</tt> in our example) to the <tt>[[$FG_AIRCRAFT]]</tt> list on the first page (previous to aircraft selection) of the launcher. Your aircraft should now show up in the list.

== When installing an aircraft fails ==
=== XML files with wrong encoding ===
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.

To fix this on Linux try this:

$ cd path/to/aircraft/directory/
$ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'

=== Rename Aircraft Folder ===
If you start FlightGear with the aircraft you installed it is invisible or if FlightGear will not start with your newly installed aircraft, but will start with other aircraft you might need to rename the aircraft folder.

If there is a readme file have a look there for instructions, otherwise try change to more obvious names like renaming for example "A320-master" to "A320" or "boeing-707" to "707". If that does not work ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the [http://forum.flightgear.org/viewforum.php?f=11 forum].

== Choosing aircraft ==
If you are looking for information to decide what aircraft to download, try:
* [[Aircraft]]
* [[Helicopter]]
* [[Vehicle]]
* [[Table of models]]
External links to third party aircraft can be found at [[FlightGear hangars]]. Remember that the latest aircraft may not load with previous versions. If you happen to use an older version of FlightGear, look for older aircraft in the links section.

== For developers ==
Help develop the [[FlightGear Package Manager]] which is intended to support automatic aircraft and scenery installation, currently in alpha development and in need of testing.

== Related content ==
* [[Installing Scenery]]

[[Category:Howto|Install aircraft]]

[[de:Howto:Flugzeuge Installieren]]
[[es:Cómo:Instalar_aviones]]
[[fr:Howto Installer un avion]]

Microsoft Windows issues

2016-03-30T15:09:21Z

Jaxsin: /* Terrasync - Known Issues */ added a link to the PowerShell script

==Can't locate data files - first time install==
{{Note|Default locations of $FG_ROOT, is the path of your installation directory. Examples are here [[$FG_ROOT]]. If you changed your installation directory during install of FlightGear then use that path instead}}
After a first time install and upon running FlightGear for the first time you see this dialog

[[File:Flightgear missing data files.PNG|Error box for FlightGear when it does not know the location of the correct data files]]

'''Resolution''' - Tell FlightGear where to find the data files that were installed. I present here 3 options. Whichever you choose, make sure you update the '''PATH''' according to your installation directory
*'''Choose Folder''' and point it to [[$FG_ROOT]]
*Paste these 3 lines inside of Notepad.exe, or some other editor, '''save as''' <code>fg-root.reg</code> file to desktop, then double click the file and add the entry to registry
{{Note|Yes, you need the double \\ in the path}}
::<syntaxhighlight lang="reg">Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\FlightGear\FlightGear]
"fg-root"="C:\\Program Files\\FlightGear 2016.1.1\\data"</syntaxhighlight>
*Open up '''regedit''' and add <code>fg-root</code> '''Key''' as a '''string''' value of [[$FG_ROOT]]

==Terrasync - Known Issues==
===Failed to remove file===
<code>file remove failed: (./.terrasync_cache) reason: Permission denied</code>

TerraSync cache files can not be deleted. You will see errors in console like above. There is not much to do other then delete the <code>.terrasync_cache</code> files manually and then run FlightGear again.

'''Resolution'''
{{Note|Not recommended. Understand the consequences}}
[http://forum.flightgear.org/viewtopic.php?f=17&t=28957&p=278275#p278275 Forum Post w/ PowerShell command is here]

Microsoft Windows issues

2016-03-30T14:16:07Z

Jaxsin: /* Can't locate data files - new install */

==Can't locate data files - first time install==
{{Note|Default locations of $FG_ROOT, is the path of your installation directory. Examples are here [[$FG_ROOT]]. If you changed your installation directory during install of FlightGear then use that path instead}}
After a first time install and upon running FlightGear for the first time you see this dialog

[[File:Flightgear missing data files.PNG|Error box for FlightGear when it does not know the location of the correct data files]]

'''Resolution''' - Tell FlightGear where to find the data files that were installed. I present here 3 options. Whichever you choose, make sure you update the '''PATH''' according to your installation directory
*'''Choose Folder''' and point it to [[$FG_ROOT]]
*Paste these 3 lines inside of Notepad.exe, or some other editor, '''save as''' <code>fg-root.reg</code> file to desktop, then double click the file and add the entry to registry
{{Note|Yes, you need the double \\ in the path}}
::<syntaxhighlight lang="reg">Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\FlightGear\FlightGear]
"fg-root"="C:\\Program Files\\FlightGear 2016.1.1\\data"</syntaxhighlight>
*Open up '''regedit''' and add <code>fg-root</code> '''Key''' as a '''string''' value of [[$FG_ROOT]]

==Terrasync - Known Issues==
===Failed to remove file===
<code>.terrasync_cache</code> files can not be deleted. You will see errors in console. There is not much to do other then delete the <code>.terrasync_cache</code> files manually and then run FlightGear again to let it recreate the up-to-date <code>.terrasync_cache</code> files.

''insert powershell script here to help with this for those that want to try.''

Microsoft Windows issues

2016-03-30T13:13:35Z

Jaxsin:

==Can't locate '''data''' files - new install==
{{Note|Default locations of $FG_ROOT, is the path of your installation directory. Examples are here [[$FG_ROOT]]. If you changed your installation directory during install of FlightGear then use that path instead}}
After a new install and upon running FlightGear for the first time you see this dialog

[[File:Flightgear missing data files.PNG|Error box for FlightGear when it does not know the location of the correct data files]]

'''Resolution''' - Tell FlightGear where to find the data files that were installed. I present here 3 options. Whichever you choose, make sure you update the '''PATH''' according to your installation directory
*'''Choose Folder''' and point it to [[$FG_ROOT]]
*Paste these 3 lines inside of Notepad.exe, or some other editor, '''save as''' <code>fg-root.reg</code> file to desktop, then double click the file and add the entry to registry
{{Note|Yes, you need the double \\ in the path}}
::<syntaxhighlight lang="reg">Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\FlightGear\FlightGear]
"fg-root"="C:\\Program Files\\FlightGear 2016.1.1\\data"</syntaxhighlight>
*Open up '''regedit''' and add <code>fg-root</code> '''Key''' as a '''string''' value of [[$FG_ROOT]]

==Terrasync - Known Issues==
===Failed to remove file===
<code>.terrasync_cache</code> files can not be deleted. You will see errors in console. There is not much to do other then delete the <code>.terrasync_cache</code> files manually and then run FlightGear again to let it recreate the up-to-date <code>.terrasync_cache</code> files.

''insert powershell script here to help with this for those that want to try.''

Microsoft Windows issues

2016-03-30T13:12:33Z

Jaxsin: Updated with proper image and streamlined the fix

{{Note|Creating this page to post solutions for new users to FlightGear on Microsoft Windows systems 7, 8.1, 10}}

==Can't locate '''data''' files - new install==
{{Note|Default locations of $FG_ROOT, is the path of your installation directory. Examples are here [[$FG_ROOT]]. If you changed your installation directory during install of FlightGear then use that path instead}}
After a new install and upon running FlightGear for the first time you see this dialog

[[File:Flightgear missing data files.PNG|Error box for FlightGear when it does not know the location of the correct data files]]

'''Resolution''' - Tell FlightGear where to find the data files that were installed. I present here 3 options. Whichever you choose, make sure you update the '''PATH''' according to your installation directory
*'''Choose Folder''' and point it to [[$FG_ROOT]]
*Paste these 3 lines inside of Notepad.exe, or some other editor, '''save as''' <code>fg-root.reg</code> file to desktop, then double click the file and add the entry to registry
{{Note|Yes, you need the double \\ in the path}}
::<syntaxhighlight lang="reg">Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\FlightGear\FlightGear]
"fg-root"="C:\\Program Files\\FlightGear 2016.1.1\\data"</syntaxhighlight>
*Open up '''regedit''' and add <code>fg-root</code> '''Key''' as a '''string''' value of [[$FG_ROOT]]

==Terrasync - Known Issues==
===Failed to remove file===
<code>.terrasync_cache</code> files can not be deleted. You will see errors in console. There is not much to do other then delete the <code>.terrasync_cache</code> files manually and then run FlightGear again to let it recreate the up-to-date <code>.terrasync_cache</code> files.

''insert powershell script here to help with this for those that want to try.''

File:Flightgear missing data files.PNG

2016-03-30T12:54:18Z

Jaxsin: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Error box for FlightGear when it does not know the location of the correct data files}}
|date=2016-03-30
|source={{own}}
|author=[[User:Jaxsin|Jaxsin]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Flightgear error dialogs]]

Microsoft Windows issues

2016-03-30T12:29:53Z

Jaxsin: /* Can't locate data files - new install */

{{Note|Creating this page to post solutions for new users to FlightGear on Microsoft Windows systems 7, 8.1, 10}}

==Can't locate '''data''' files - new install==
'''''Known bug'''''
*'''Resolution''' - Tell FlightGear where to find the data files that were installed.
:::''post img here''
:::You can also paste these 3 lines inside of Notepad and '''save as''' <code>fg-root.reg</code> file to desktop, then double click the file and add the entry to registry
::::<syntaxhighlight lang="reg">Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\FlightGear\FlightGear]
"fg-root"="C:\\Program Files\\FlightGear 2016.1.1\\data"</syntaxhighlight>
:::Open up '''regedit''' and add <code>fg-root</code> key.

==Terrasync - Known Issues==
===Failed to remove file===
<code>.terrasync_cache</code> files can not be deleted. You will see errors in console. There is not much to do other then delete the <code>.terrasync_cache</code> files manually and then run FlightGear again to let it recreate the up-to-date <code>.terrasync_cache</code> files.

''insert powershell script here to help with this for those that want to try.''

Microsoft Windows issues

2016-03-30T12:16:15Z

Jaxsin: Started to help new Windows users get going

{{Note|Creating this page to post solutions for new users to FlightGear on Microsoft Windows systems 7, 8.1, 10}}

==Can't locate '''data''' files - new install==
'''''Known bug'''''
*'''Resolution''' - Tell FlightGear where to find the data files that were installed.
:::''post img here''
:::You can also paste these 3 lines inside of Notepad and '''save as''' fg-root.reg to desktop, then double click the file and add the entry to registry
::::<syntaxhighlight lang="reg">Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\FlightGear\FlightGear]
"fg-root"="C:\\Program Files\\FlightGear 2016.1.1\\data"</syntaxhighlight>
:::Open up '''regedit''' and add <code>fg-root</code> key.

==Terrasync - Known Issues==
===Failed to remove file===
<code>.terrasync_cache</code> files can not be deleted. You will see errors in console. There is not much to do other then delete the <code>.terrasync_cache</code> files manually and then run FlightGear again to let it recreate the up-to-date <code>.terrasync_cache</code> files.

''insert powershell script here to help with this for those that want to try.''

$FG ROOT

2016-03-30T09:59:00Z

Jaxsin:

The environment variable <code>'''$FG_ROOT'''</code> is referring to the path of the main data directory of [[FlightGear]], which contains the so called ''base package''. The base package consists of the default [[aircraft]] and [[scenery]], [[Menubar|GUI]] files, sounds, 3D models etc.

When running FlightGear from a [[command line]], you can set <code>$FG_ROOT</code> via <code>--fg-root=path/to/root</code>. In [[FGRun]], it is set on the paths page, previous to the aircraft selection page.

As of FlightGear 2.4, it is advised to install additional scenery and aircraft in <code>[[$FG_SCENERY]]</code> and <code>[[$FG_AIRCRAFT]]</code> directories outside <code>$FG_ROOT</code>. This allow for maintaining the additional stuff when installing a new version of FlightGear.

== Common paths ==
* '''Mac OS X:''' <code>Applications/FlightGear.app/Contents/Resources/data/</code> (right-click on FlightGear.app and select "Show Package Contents" to see the Contents folder)
: <code>$FG_ROOT</code> is not installed automatically. See [[New to FlightGear#Installing on Mac OS X|New to FlightGear]] for an installation manual.
* '''Ubuntu:''' <code>/usr/share/games/flightgear/</code>
* '''Windows:''' <code>Program Files\FlightGear 2016.1.1\data\</code> (default, '''see note!''')

{{note|Newer '''Windows''' versions are very, very protective about the '''<code>Program Files</code> folder'''.

Installing FlightGear into this folder makes it prone to any problems relating to file read/write permissions. Hence, installing FlightGear into <code>Program Files</code> on Windows Vista and later is not recommended. ''(I have yet to see where installing it outside of the default location actually helps - '''jaxsin''')''}}

== $FG_DATA ==
You will sometimes see <code>$FG_ROOT</code> erroneously being mentioned as <code>'''$FG_DATA'''</code>. While there is no <code>$FG_DATA</code> environment variable, the SourceForge repository containing the base package is named <code>[[FGData]]</code> and was earlier named <code>fgdata</code> in Gitorious.<ref>https://www.mail-archive.com/search?q=fgdata&l=flightgear-devel%40lists.sourceforge.net</ref><ref>https://www.mail-archive.com/search?l=flightgear-devel%40lists.sourceforge.net&q=fg_data&x=0&y=0</ref>

== References ==
<references/>
[[Category:Special directories|ROOT]]

[[de:$FG ROOT]]
[[fr:$FG ROOT]]
[[nl:$FG_ROOT]]
[[es:$FG_ROOT]]

$FG ROOT

2016-03-30T09:57:53Z

Jaxsin:

The environment variable <code>'''$FG_ROOT'''</code> is referring to the path of the main data directory of [[FlightGear]], which contains the so called ''base package''. The base package consists of the default [[aircraft]] and [[scenery]], [[Menubar|GUI]] files, sounds, 3D models etc.

When running FlightGear from a [[command line]], you can set <code>$FG_ROOT</code> via <code>--fg-root=path/to/root</code>. In [[FGRun]], it is set on the paths page, previous to the aircraft selection page.

As of FlightGear 2.4, it is advised to install additional scenery and aircraft in <code>[[$FG_SCENERY]]</code> and <code>[[$FG_AIRCRAFT]]</code> directories outside <code>$FG_ROOT</code>. This allow for maintaining the additional stuff when installing a new version of FlightGear.

== Common paths ==
* '''Mac OS X:''' <code>Applications/FlightGear.app/Contents/Resources/data/</code> (right-click on FlightGear.app and select "Show Package Contents" to see the Contents folder)
: <code>$FG_ROOT</code> is not installed automatically. See [[New to FlightGear#Installing on Mac OS X|New to FlightGear]] for an installation manual.
* '''Ubuntu:''' <code>/usr/share/games/flightgear/</code>
* '''Windows:''' <code>Program Files\FlightGear 2016.1.1\data\</code> (default, '''see note!''')

{{note|Newer '''Windows''' versions are very, very protective about the '''<code>Program Files</code> folder'''.

Installing FlightGear into this folder makes it prone to any problems relating to file read/write permissions. Hence, installing FlightGear into <code>Program Files</code> on Windows Vista and later is not recommended. (I have yet to see where installing it outside of the default location actually helps - jaxsin}}

== $FG_DATA ==
You will sometimes see <code>$FG_ROOT</code> erroneously being mentioned as <code>'''$FG_DATA'''</code>. While there is no <code>$FG_DATA</code> environment variable, the SourceForge repository containing the base package is named <code>[[FGData]]</code> and was earlier named <code>fgdata</code> in Gitorious.<ref>https://www.mail-archive.com/search?q=fgdata&l=flightgear-devel%40lists.sourceforge.net</ref><ref>https://www.mail-archive.com/search?l=flightgear-devel%40lists.sourceforge.net&q=fg_data&x=0&y=0</ref>

== References ==
<references/>
[[Category:Special directories|ROOT]]

[[de:$FG ROOT]]
[[fr:$FG ROOT]]
[[nl:$FG_ROOT]]
[[es:$FG_ROOT]]

Atlas

2016-03-27T11:31:02Z

Jaxsin: Obsolete information. Needs author input to remove or update

{{Obsolete|Phi}}

{{forum|31|Atlas}}
[[File:Atlas.jpg|thumb|270px|Atlas map view of the San Francisco bay area]]

''"Atlas aims to produce and display high quality charts of the World for users of FlightGear"'' - [http://atlas.sourceforge.net Atlas website]

== Introduction ==
The '''Atlas''' program lets FlightGear users display a real-time "moving-map" of their flight. Atlas is an independent software project, distributed under the same free (GPL) software license as FlightGear.

== Installation (only for 0.3.x version) ==

=== Installing on Windows ===
To install Atlas on Windows, download the "installer" version of Atlas from the [http://atlas.sourceforge.net/index.php?page=download Download Page]

For example, download '''atlas-0.3.0-win32-setup.exe''', and run it. The installer will prompt you for the FlightGear directory. If you installed FlightGear in the default directory, "C:\Program Files\FlightGear", accept the default setting. If you don't know your FlightGear directory, you can right-click your FlightGear icon, click properties then look at the "target". Your root FlightGear directory is the part of the target before the text "\bin\win32\fgrun.exe")

After finishing the install wizard, but before running Atlas, the next step is to create the actual maps used by Atlas.

=== Installing on Linux ===

If you are lucky, you might find that Atlas is available from your distribution's repository.

It could be called fgfs-atlas or similar so you'd just type in the following (or use synaptic or some other package installation program):-

apt-get install fgfs-atlas

If you distribution doesn't include a current version of Atlas (0.3.1 as of writing), you may elect to compile Atlas from source. The source code can be retrieved from http://sourceforge.net/projects/atlas/files/. Please select the latest tarball. The process of compiling the program is consider out of scope for this wiki page. Please ask on the mailing list or search this wiki for the details.

=== Creating the Maps ===
Atlas puts together the whole map display from smaller pieces of the map, called "tiles". Before running Atlas for the first time, all of the map tiles used by Atlas must be created from the scenery data installed in FlightGear. The program used to create the tiles is called "map", and it is installed automatically as part of the Atlas installation.

Depending on the amount of scenery involved, and the level of detail requested, running the "map" process take anywhere from a few seconds to a few hours. Fortunately, this process does not need to be done often, only right after Atlas is installed, or after new scenery is added to FlightGear.

Here is an example of how to run "map" on Windows:

This example uses the default FlightGear directory for Windows, C:\Program Files\FlightGear. If you have FlightGear installed somewhere else, substitute your directory in the instructions below.

Start the Command Prompt...to do this click start>Run ...type cmd and hit enter.
Type...
cd C:\Program Files\FlightGear\bin\win32
Now Type...
set FG_ROOT=C:\Program Files\FlightGear\data
Now type...
set FG_SCENERY=C:\Program Files\FlightGear\Data\Scenery;C:\Program Files\FlightGear\Scenery
Notice that the scenery directories are separated with a semi-colon (";").
Now type
map --size=256 --atlas=C:\Program Files\FlightGear\data\Atlas
This puts the files in <tt>C:\Program Files\FlightGear\data\Atlas</tt>. If you want the files in a different location just replace <tt>C:\Program Files\FlightGear\data\Atlas</tt> with the location you want.

The --size=256 gives a certain resolution in Atlas, meaning that each map generated will be 256x256 pixels. For higher resolutions you would use =512 or =1024 or =2048, for lower resolutions you would use =64 or =128.

Therefore, to create low resolution maps type...
map --size=64 --atlas=C:\Program Files\FlightGear\data\Atlas\lowres

The map program has a lot commands-line options. To see them type...
map --help
To see this message
<tt>
MAP - FlightGear mapping utility
Usage:
--lat=xx.xx Start at latitude xx.xx (deg., south is neg.)
--lon=xx.xx Start at longitude xx.xx (deg., west is neg.)
--size=pixels Create map of size pixels*pixels (default 256)
--scale=x Kilometers from top to bottom of map (default 100)
--autoscale Automatically set scale to 1x1 degree tile
--light=x, y, z Set light vector for shading
--airport-filter=string Display only airports with id beginning 'string'
--output=name Write output to given file name (default 'map.png')
--fg-root=path Overrides FG_ROOT environment variable
--fg-scenery=path Overrides FG_SCENERY environment variable
--enable-airports Show airports
--enable-navaids Show navaids
--flat-shading Don't do nice shading of the terrain
--atlas=path Create maps of all scenery, and store them in path
--verbose Display information during processing
--singlebuffer Use single buffered display
--headless Don't display output (render into an off-screen buffer)
--glutfonts Use GLUT built-in fonts
--palette=path Set the palette file to use
--smooth-color Make smooth color heights
--jpeg Create JPEG images with default quality (75)
--jpeg=integer Create JPEG images with specified quality
--aafactor=integer Do antialiasing on image (factor must be a power of two)
</tt>

* '''Note 1:''' The map process can be much faster on some PC's using '''--headless''' option, which does not display the maps as they are being created. However, on other PC's, this causes an error, and the process will not run. Remove the '''--headless''' option if you get such an error.
* '''Note 2:''' On Windows systems, Atlas may not be able to handle paths for <tt>--atlas</tt> with spaces in them. In such a case, replace "Program Files" with "PROGRA~1". Or move the FG directory and Atlas directory to the desktop (works best with windows 7).

You could condense this into a small batch file that can be repeatedly used. Write:
cd c:\Program Files\Atlas\bin\win32
map --size=512 --atlas=c:\Program Files\Atlas\data\Atlas --fg-scenery=c:\Program Files\FlightGear\data\Scenery --palette=c:\Program Files\Atlas\data\AtlasPalette --glutfonts

Then save it as a .bat or .cmd file to your computer. If your computer turns off the screen / hard drive after a set time and don't want to change this permanently, download caffeine. Search for caffeine for windows on Google and select the first link.

=== Run Atlas ===
Atlas can be run by clicking on the shortcut set up by the install wizard, or from the command line. From the command prompt in Windows, enter:
"C:\Program Files\FlightGear\bin\win32\atlas.exe" "--fg-root=C:\Program Files\FlightGear\Data" "--path=C:\Program Files\FlightGear\data\Atlas" --udp=5500

In the [[FlightGear Wizard]] where you select settings before starting FlightGear, on the page after selecting your airport there is a check box option for Atlas, check it. In the "port" box enter 5500. If Atlas is running on the same computer as FlightGear, you can use the IP address 127.0.0.1 If Atlas is running on another computer, enter the IP address of that computer. (To look up the IP address of a computer, open the command prompt, and enter "ipconfig" as a command to display the IP address).

Once you have Atlas and FlightGear set to use the same port number (5500 by default), run FlightGear. As you fly around in FlightGear, Atlas will update your position on the map several times per second.

===Running Atlas Over A Network===
If you installed atlas on a computer, but want to run it from a different one, follow this procedure:
For Windows, on your first computer (the one with FlightGear and Atlas) enable file sharing. After doing this, if you have a firewall, go to your second computer and open the Command Prompt (Windows + R, then type "CMD") and type:
"ipconfig"
and note the IPv4 Address (along the lines of 192.168.1.XX) and add a firewall rule on your first computer to let that IP address through the firewall. Then set up the files for file sharing. Go to your FlightGear program files folder (C:\Program Files (x86)\FlightGear) and right click and select properties. Select the "Sharing" tab and click "Advanced Sharing". Click the checkbox for "Share this folder" and push "OK" on both windows. Do the same for the Atlas program folder (C:\Program Files (x86)\Atlas).

On your first computer, open the CMD and do "ipconfig" and note the IPv4 address. Go to your second computer and right click the "My Computer" and select "Map Network Drive". Leave the drive setting alone, Windows will configure that itself. In the "Path" box, type without the "":
"\\XXX.XXX.X.XX\FlightGear"
The "X" representing the numbers of the first computers IPv4 address.
Repeat this for the Atlas folder by changing "\FlightGear" to "\Atlas". Also note the \\. It is REQUIRED you do that and not //.

Once you have done this write a ".CMD" file in Notepad which would read:

title Atlas.exe
cls
@echo off
cls
ipconfig
pause
"W:\bin\win32\atlas.exe" "--fg-root=X:\Data" "--path=W:\data\Atlas" --udp=5500

The "W" drive is the Atlas folder in this example, change it to whatever Windows sets as your Atlas drive.
The "X" drive is the FlightGear folder in this example, change it to whatever Windows sets as your FlightGear drive.

The first line sets the CMD window name. The second line clears the window. The third line turns off the echo (if it was left on, the CMD would repeat what the batch file tells it, for example, if it was off, the cmd would run and say C:\Documents and Settings\User> title atlas.exe). The fourth line clears the window. The fifth line gives the IP address. The sixth line pauses and reads "Push any key to continue...". The seventh line executes the atlas program with the specified settings.

Once you are done with the script, click "File>Save As..." and save it as Start Atlas.bat (or .cmd).

You will need the scenery analyzed by the map.exe first. So if that is done, execute the file and wait for it to tell you the IPv4 address. Go to your first computer and configure your flight. On the final page, select the Atlas checkbox and enter the IPv4 address of the second computer and the UDP (default "5500") to what you set as the final part of the seventh line of coding. On the second computer, push any key and the Command Prompt will load the Atlas database can take some time if you are using all of the scenery maps. When the atlas window opens, activate the flight on the second computer and you have the second computer tracking the flight of the first. (don't worry the FlightGear App defaults to the e0 n0 co-ordinates at startup without loading the map graphics.)

=== Keys ===
You can control the Atlas Map display with the following keys:

{|
|-
| width="70px" | + || Zoom in
|-
| - || Zoom out
|-
| a/A || Show/hide Airports
|-
| C || Toggle auto-centering
|-
| c || Center map on Aircraft
|-
| d/D
| Hide/show the info interface and the graphs window
|-
| f/F
| Select next (f) or previous (F) flight track
|-
| j/J || Toggle search interface
|-
| L || Show the next downloading tile
|-
| l
| Schedule/de-schedule tile at current lat/lon
|-
| n/N || Show/hide navaids
|-
| o/O || Open flight file
|-
| s/S || Save flight file
|-
| t/T
| Toggle showing the bitmap overlay (yes, that's the maps!)
|-
| w/W
| Close the current track (Warning, this terminates live aircraft tracking over network for good!)
|-
| u/U
| Unattach current flight trac, ie start a new track
|-
| v/V
| Show/hide names of airports/navaids
|-
| Space || Show/hide main interface
|}

'''Enjoy Playing!!!'''

== Similar Software ==
* [http://rubyforge.org/projects/fgmap Flightgear Mapping]

== External links ==
* [http://atlas.sourceforge.net The Atlas website]
[[fr:Atlas]]
* [http://geoffmclane.com/fg/atlas-07.htm Windows build, by Geoff McLane]
[[Category:Software]]
[[Category:GPL software]]

Atlas

2016-03-27T11:06:16Z

Jaxsin: Updated with a note to show this is deprecated and Phi is the alternative local map.

{{Note|Should be considered deprecated. An alternative [[Phi]]}}

{{forum|31|Atlas}}
[[File:Atlas.jpg|thumb|270px|Atlas map view of the San Francisco bay area]]

''"Atlas aims to produce and display high quality charts of the World for users of FlightGear"'' - [http://atlas.sourceforge.net Atlas website]

== Introduction ==
The '''Atlas''' program lets FlightGear users display a real-time "moving-map" of their flight. Atlas is an independent software project, distributed under the same free (GPL) software license as FlightGear.

== Installation (only for 0.3.x version) ==

=== Installing on Windows ===
To install Atlas on Windows, download the "installer" version of Atlas from the [http://atlas.sourceforge.net/index.php?page=download Download Page]

For example, download '''atlas-0.3.0-win32-setup.exe''', and run it. The installer will prompt you for the FlightGear directory. If you installed FlightGear in the default directory, "C:\Program Files\FlightGear", accept the default setting. If you don't know your FlightGear directory, you can right-click your FlightGear icon, click properties then look at the "target". Your root FlightGear directory is the part of the target before the text "\bin\win32\fgrun.exe")

After finishing the install wizard, but before running Atlas, the next step is to create the actual maps used by Atlas.

=== Installing on Linux ===

If you are lucky, you might find that Atlas is available from your distribution's repository.

It could be called fgfs-atlas or similar so you'd just type in the following (or use synaptic or some other package installation program):-

apt-get install fgfs-atlas

If you distribution doesn't include a current version of Atlas (0.3.1 as of writing), you may elect to compile Atlas from source. The source code can be retrieved from http://sourceforge.net/projects/atlas/files/. Please select the latest tarball. The process of compiling the program is consider out of scope for this wiki page. Please ask on the mailing list or search this wiki for the details.

=== Creating the Maps ===
Atlas puts together the whole map display from smaller pieces of the map, called "tiles". Before running Atlas for the first time, all of the map tiles used by Atlas must be created from the scenery data installed in FlightGear. The program used to create the tiles is called "map", and it is installed automatically as part of the Atlas installation.

Depending on the amount of scenery involved, and the level of detail requested, running the "map" process take anywhere from a few seconds to a few hours. Fortunately, this process does not need to be done often, only right after Atlas is installed, or after new scenery is added to FlightGear.

Here is an example of how to run "map" on Windows:

This example uses the default FlightGear directory for Windows, C:\Program Files\FlightGear. If you have FlightGear installed somewhere else, substitute your directory in the instructions below.

Start the Command Prompt...to do this click start>Run ...type cmd and hit enter.
Type...
cd C:\Program Files\FlightGear\bin\win32
Now Type...
set FG_ROOT=C:\Program Files\FlightGear\data
Now type...
set FG_SCENERY=C:\Program Files\FlightGear\Data\Scenery;C:\Program Files\FlightGear\Scenery
Notice that the scenery directories are separated with a semi-colon (";").
Now type
map --size=256 --atlas=C:\Program Files\FlightGear\data\Atlas
This puts the files in <tt>C:\Program Files\FlightGear\data\Atlas</tt>. If you want the files in a different location just replace <tt>C:\Program Files\FlightGear\data\Atlas</tt> with the location you want.

The --size=256 gives a certain resolution in Atlas, meaning that each map generated will be 256x256 pixels. For higher resolutions you would use =512 or =1024 or =2048, for lower resolutions you would use =64 or =128.

Therefore, to create low resolution maps type...
map --size=64 --atlas=C:\Program Files\FlightGear\data\Atlas\lowres

The map program has a lot commands-line options. To see them type...
map --help
To see this message
<tt>
MAP - FlightGear mapping utility
Usage:
--lat=xx.xx Start at latitude xx.xx (deg., south is neg.)
--lon=xx.xx Start at longitude xx.xx (deg., west is neg.)
--size=pixels Create map of size pixels*pixels (default 256)
--scale=x Kilometers from top to bottom of map (default 100)
--autoscale Automatically set scale to 1x1 degree tile
--light=x, y, z Set light vector for shading
--airport-filter=string Display only airports with id beginning 'string'
--output=name Write output to given file name (default 'map.png')
--fg-root=path Overrides FG_ROOT environment variable
--fg-scenery=path Overrides FG_SCENERY environment variable
--enable-airports Show airports
--enable-navaids Show navaids
--flat-shading Don't do nice shading of the terrain
--atlas=path Create maps of all scenery, and store them in path
--verbose Display information during processing
--singlebuffer Use single buffered display
--headless Don't display output (render into an off-screen buffer)
--glutfonts Use GLUT built-in fonts
--palette=path Set the palette file to use
--smooth-color Make smooth color heights
--jpeg Create JPEG images with default quality (75)
--jpeg=integer Create JPEG images with specified quality
--aafactor=integer Do antialiasing on image (factor must be a power of two)
</tt>

* '''Note 1:''' The map process can be much faster on some PC's using '''--headless''' option, which does not display the maps as they are being created. However, on other PC's, this causes an error, and the process will not run. Remove the '''--headless''' option if you get such an error.
* '''Note 2:''' On Windows systems, Atlas may not be able to handle paths for <tt>--atlas</tt> with spaces in them. In such a case, replace "Program Files" with "PROGRA~1". Or move the FG directory and Atlas directory to the desktop (works best with windows 7).

You could condense this into a small batch file that can be repeatedly used. Write:
cd c:\Program Files\Atlas\bin\win32
map --size=512 --atlas=c:\Program Files\Atlas\data\Atlas --fg-scenery=c:\Program Files\FlightGear\data\Scenery --palette=c:\Program Files\Atlas\data\AtlasPalette --glutfonts

Then save it as a .bat or .cmd file to your computer. If your computer turns off the screen / hard drive after a set time and don't want to change this permanently, download caffeine. Search for caffeine for windows on Google and select the first link.

=== Run Atlas ===
Atlas can be run by clicking on the shortcut set up by the install wizard, or from the command line. From the command prompt in Windows, enter:
"C:\Program Files\FlightGear\bin\win32\atlas.exe" "--fg-root=C:\Program Files\FlightGear\Data" "--path=C:\Program Files\FlightGear\data\Atlas" --udp=5500

In the [[FlightGear Wizard]] where you select settings before starting FlightGear, on the page after selecting your airport there is a check box option for Atlas, check it. In the "port" box enter 5500. If Atlas is running on the same computer as FlightGear, you can use the IP address 127.0.0.1 If Atlas is running on another computer, enter the IP address of that computer. (To look up the IP address of a computer, open the command prompt, and enter "ipconfig" as a command to display the IP address).

Once you have Atlas and FlightGear set to use the same port number (5500 by default), run FlightGear. As you fly around in FlightGear, Atlas will update your position on the map several times per second.

===Running Atlas Over A Network===
If you installed atlas on a computer, but want to run it from a different one, follow this procedure:
For Windows, on your first computer (the one with FlightGear and Atlas) enable file sharing. After doing this, if you have a firewall, go to your second computer and open the Command Prompt (Windows + R, then type "CMD") and type:
"ipconfig"
and note the IPv4 Address (along the lines of 192.168.1.XX) and add a firewall rule on your first computer to let that IP address through the firewall. Then set up the files for file sharing. Go to your FlightGear program files folder (C:\Program Files (x86)\FlightGear) and right click and select properties. Select the "Sharing" tab and click "Advanced Sharing". Click the checkbox for "Share this folder" and push "OK" on both windows. Do the same for the Atlas program folder (C:\Program Files (x86)\Atlas).

On your first computer, open the CMD and do "ipconfig" and note the IPv4 address. Go to your second computer and right click the "My Computer" and select "Map Network Drive". Leave the drive setting alone, Windows will configure that itself. In the "Path" box, type without the "":
"\\XXX.XXX.X.XX\FlightGear"
The "X" representing the numbers of the first computers IPv4 address.
Repeat this for the Atlas folder by changing "\FlightGear" to "\Atlas". Also note the \\. It is REQUIRED you do that and not //.

Once you have done this write a ".CMD" file in Notepad which would read:

title Atlas.exe
cls
@echo off
cls
ipconfig
pause
"W:\bin\win32\atlas.exe" "--fg-root=X:\Data" "--path=W:\data\Atlas" --udp=5500

The "W" drive is the Atlas folder in this example, change it to whatever Windows sets as your Atlas drive.
The "X" drive is the FlightGear folder in this example, change it to whatever Windows sets as your FlightGear drive.

The first line sets the CMD window name. The second line clears the window. The third line turns off the echo (if it was left on, the CMD would repeat what the batch file tells it, for example, if it was off, the cmd would run and say C:\Documents and Settings\User> title atlas.exe). The fourth line clears the window. The fifth line gives the IP address. The sixth line pauses and reads "Push any key to continue...". The seventh line executes the atlas program with the specified settings.

Once you are done with the script, click "File>Save As..." and save it as Start Atlas.bat (or .cmd).

You will need the scenery analyzed by the map.exe first. So if that is done, execute the file and wait for it to tell you the IPv4 address. Go to your first computer and configure your flight. On the final page, select the Atlas checkbox and enter the IPv4 address of the second computer and the UDP (default "5500") to what you set as the final part of the seventh line of coding. On the second computer, push any key and the Command Prompt will load the Atlas database can take some time if you are using all of the scenery maps. When the atlas window opens, activate the flight on the second computer and you have the second computer tracking the flight of the first. (don't worry the FlightGear App defaults to the e0 n0 co-ordinates at startup without loading the map graphics.)

=== Keys ===
You can control the Atlas Map display with the following keys:

{|
|-
| width="70px" | + || Zoom in
|-
| - || Zoom out
|-
| a/A || Show/hide Airports
|-
| C || Toggle auto-centering
|-
| c || Center map on Aircraft
|-
| d/D
| Hide/show the info interface and the graphs window
|-
| f/F
| Select next (f) or previous (F) flight track
|-
| j/J || Toggle search interface
|-
| L || Show the next downloading tile
|-
| l
| Schedule/de-schedule tile at current lat/lon
|-
| n/N || Show/hide navaids
|-
| o/O || Open flight file
|-
| s/S || Save flight file
|-
| t/T
| Toggle showing the bitmap overlay (yes, that's the maps!)
|-
| w/W
| Close the current track (Warning, this terminates live aircraft tracking over network for good!)
|-
| u/U
| Unattach current flight trac, ie start a new track
|-
| v/V
| Show/hide names of airports/navaids
|-
| Space || Show/hide main interface
|}

'''Enjoy Playing!!!'''

== Similar Software ==
* [http://rubyforge.org/projects/fgmap Flightgear Mapping]

== External links ==
* [http://atlas.sourceforge.net The Atlas website]
[[fr:Atlas]]
* [http://geoffmclane.com/fg/atlas-07.htm Windows build, by Geoff McLane]
[[Category:Software]]
[[Category:GPL software]]

Talk:Phi

2016-03-23T13:47:27Z

Jaxsin:

@jaxsin: thanks for doing this, I am sure that Torsten also appreciates that you are handling all this grunt work, and that he'll be happy to chime in with any missing information. In th meantime, you may want to take a look at [[Help:Your_first_article]] to see how you can better format the article. Again, thanks for not just pointing out that there's a problem but for getting involved to do something to improve the situation.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:16, 21 March 2016 (EDT)

@hooray: concerning the [[Phi#Background]] sub-section. These are direct quotes from Torsten, I wanted to leave them as genuine as possible and mark them with the reference. Which I have done. But the overall appearance of them being quotes (without the silly looking quotes) is not very well conveyed. I am not sure how I can improve that. Any improvement here that I can pick up moving forward I'd appreciate it.

Phi

2016-03-23T13:40:51Z

Jaxsin: /* Background */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==
''Direct quotes from '''Torsten'''. Original '''Phi''' developer''

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Phi UI Features ==
Phi is at foremost a multi-platform user interface that has two-way data binding with FlightGear via the internal HTTP web server. This allows Phi to be a fully functional user interface that can directly control FlightGear. The following list is a set of features that are currently implemented and working.
=== Aircraft ===
This is where you will find all things related to the currently selected aircraft in-sim, if available.
*'''Help''' - Displays the aircraft help file '''Help > Aircraft Help'''
*'''Mass & Balance''' - Displays aircraft specific fuel and payload options '''Equipment > Fuel and Payload'''
*'''Checklist''' - Displays aircraft checklist '''Help > '''
*'''Failures''' -
*'''Panel''' -
*'''Select''' - ''Known bug in FG for windows versions 7+, assume this feature to not work anytime soon even if you see a list of planes to install''
=== Environment===
*'''Date & Time''' - Change in-sim time of day and current date
*'''Weather''' -
*'''Position''' - Interface where you can search for airports via ICAO codes and then select a runway/parking spot to load into FlightGear '''Location > Select Airport'''
=== Map ===
Loads an OpenStreetMap as the background and updates your current position around the world in real time while you fly. Allows one to not only track current flight, but the ability to drag the plane icon around the map which will instantly update FlightGear with the new lon. and lat. coordinate position.
=== Tools===
Things that make for a more realistic experience. Not exactly needed to fly a plane, but these tools will add to the realism.
*'''Holding Pattern''' - A tool to help one understand how to enter the holding pattern. Enter in the Heading and Inbound Track and the diagram will show you visually the Holding pattern.
*'''Wind Calculator''' -
*'''Vertical Navigation (VNAV)''' - ''from my understanding not anytime soon, needs FG integration first''
*'''Stopwatch''' - Self-explanatory
=== Simulator ===
*'''Screenshot''' - Set the time between screen updates. See [[Phi#Screen Shots]]
*'''Properties''' - In-sim property tree, two-way data binding, good for debugging!
*'''Config''' - In-sim config settings
**'''AI''' - Enable/Disable AI
**'''Multi-Player''' - Enter callsign and select which server to connect to on the multi-player network.
*'''Reset''' - Reset the FlightGear Sim
*'''Exit''' - Quit

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

=== Making Web-Panel instruments ===
{{Note| This section should be considered unfinished. If you have something to add, please do so}}
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
Here you can find code examples that have been added to the Phi project
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/
The Horizon example is a fat free, stripped down basic idea of a web based instrument for Phi.
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.html
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.js

== Future Development ==
{{Note|Nothing concrete}}
*improve the aircraft specific plugin system to allow special widgets and pages for aircraft (thinking of the shuttle here)
*make layout and theme configurable
*keep settings persistent between sessions
*write a tile renderer to create map tiles from scenery
*better support for touch events
*together with ThorstenR: UI to configure a 3d weather model

== References ==

Phi

2016-03-23T13:35:49Z

Jaxsin: /* Web-based EFIS */ Moved from #Background

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Phi UI Features ==
Phi is at foremost a multi-platform user interface that has two-way data binding with FlightGear via the internal HTTP web server. This allows Phi to be a fully functional user interface that can directly control FlightGear. The following list is a set of features that are currently implemented and working.
=== Aircraft ===
This is where you will find all things related to the currently selected aircraft in-sim, if available.
*'''Help''' - Displays the aircraft help file '''Help > Aircraft Help'''
*'''Mass & Balance''' - Displays aircraft specific fuel and payload options '''Equipment > Fuel and Payload'''
*'''Checklist''' - Displays aircraft checklist '''Help > '''
*'''Failures''' -
*'''Panel''' -
*'''Select''' - ''Known bug in FG for windows versions 7+, assume this feature to not work anytime soon even if you see a list of planes to install''
=== Environment===
*'''Date & Time''' - Change in-sim time of day and current date
*'''Weather''' -
*'''Position''' - Interface where you can search for airports via ICAO codes and then select a runway/parking spot to load into FlightGear '''Location > Select Airport'''
=== Map ===
Loads an OpenStreetMap as the background and updates your current position around the world in real time while you fly. Allows one to not only track current flight, but the ability to drag the plane icon around the map which will instantly update FlightGear with the new lon. and lat. coordinate position.
=== Tools===
Things that make for a more realistic experience. Not exactly needed to fly a plane, but these tools will add to the realism.
*'''Holding Pattern''' - A tool to help one understand how to enter the holding pattern. Enter in the Heading and Inbound Track and the diagram will show you visually the Holding pattern.
*'''Wind Calculator''' -
*'''Vertical Navigation (VNAV)''' - ''from my understanding not anytime soon, needs FG integration first''
*'''Stopwatch''' - Self-explanatory
=== Simulator ===
*'''Screenshot''' - Set the time between screen updates. See [[Phi#Screen Shots]]
*'''Properties''' - In-sim property tree, two-way data binding, good for debugging!
*'''Config''' - In-sim config settings
**'''AI''' - Enable/Disable AI
**'''Multi-Player''' - Enter callsign and select which server to connect to on the multi-player network.
*'''Reset''' - Reset the FlightGear Sim
*'''Exit''' - Quit

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

=== Making Web-Panel instruments ===
{{Note| This section should be considered unfinished. If you have something to add, please do so}}
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
Here you can find code examples that have been added to the Phi project
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/
The Horizon example is a fat free, stripped down basic idea of a web based instrument for Phi.
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.html
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.js

== Future Development ==
{{Note|Nothing concrete}}
*improve the aircraft specific plugin system to allow special widgets and pages for aircraft (thinking of the shuttle here)
*make layout and theme configurable
*keep settings persistent between sessions
*write a tile renderer to create map tiles from scenery
*better support for touch events
*together with ThorstenR: UI to configure a 3d weather model

== References ==

Phi

2016-03-23T13:34:25Z

Jaxsin: /* Background */ moved to the appropriate sub-section #Web-based EFIS

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Phi UI Features ==
Phi is at foremost a multi-platform user interface that has two-way data binding with FlightGear via the internal HTTP web server. This allows Phi to be a fully functional user interface that can directly control FlightGear. The following list is a set of features that are currently implemented and working.
=== Aircraft ===
This is where you will find all things related to the currently selected aircraft in-sim, if available.
*'''Help''' - Displays the aircraft help file '''Help > Aircraft Help'''
*'''Mass & Balance''' - Displays aircraft specific fuel and payload options '''Equipment > Fuel and Payload'''
*'''Checklist''' - Displays aircraft checklist '''Help > '''
*'''Failures''' -
*'''Panel''' -
*'''Select''' - ''Known bug in FG for windows versions 7+, assume this feature to not work anytime soon even if you see a list of planes to install''
=== Environment===
*'''Date & Time''' - Change in-sim time of day and current date
*'''Weather''' -
*'''Position''' - Interface where you can search for airports via ICAO codes and then select a runway/parking spot to load into FlightGear '''Location > Select Airport'''
=== Map ===
Loads an OpenStreetMap as the background and updates your current position around the world in real time while you fly. Allows one to not only track current flight, but the ability to drag the plane icon around the map which will instantly update FlightGear with the new lon. and lat. coordinate position.
=== Tools===
Things that make for a more realistic experience. Not exactly needed to fly a plane, but these tools will add to the realism.
*'''Holding Pattern''' - A tool to help one understand how to enter the holding pattern. Enter in the Heading and Inbound Track and the diagram will show you visually the Holding pattern.
*'''Wind Calculator''' -
*'''Vertical Navigation (VNAV)''' - ''from my understanding not anytime soon, needs FG integration first''
*'''Stopwatch''' - Self-explanatory
=== Simulator ===
*'''Screenshot''' - Set the time between screen updates. See [[Phi#Screen Shots]]
*'''Properties''' - In-sim property tree, two-way data binding, good for debugging!
*'''Config''' - In-sim config settings
**'''AI''' - Enable/Disable AI
**'''Multi-Player''' - Enter callsign and select which server to connect to on the multi-player network.
*'''Reset''' - Reset the FlightGear Sim
*'''Exit''' - Quit

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
{{Note| This section should be considered unfinished. If you have something to add, please do so}}
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
Here you can find code examples that have been added to the Phi project
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/
The Horizon example is a fat free, stripped down basic idea of a web based instrument for Phi.
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.html
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.js

== Future Development ==
{{Note|Nothing concrete}}
*improve the aircraft specific plugin system to allow special widgets and pages for aircraft (thinking of the shuttle here)
*make layout and theme configurable
*keep settings persistent between sessions
*write a tile renderer to create map tiles from scenery
*better support for touch events
*together with ThorstenR: UI to configure a 3d weather model

== References ==

Phi

2016-03-23T13:20:21Z

Jaxsin: future developments, updated Examples, and removed Note - should be considered ready for consumption

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

''Not exactly appropriate for the Phi wiki page, leaving till I find something more relevant''
{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Phi UI Features ==
Phi is at foremost a multi-platform user interface that has two-way data binding with FlightGear via the internal HTTP web server. This allows Phi to be a fully functional user interface that can directly control FlightGear. The following list is a set of features that are currently implemented and working.
=== Aircraft ===
This is where you will find all things related to the currently selected aircraft in-sim, if available.
*'''Help''' - Displays the aircraft help file '''Help > Aircraft Help'''
*'''Mass & Balance''' - Displays aircraft specific fuel and payload options '''Equipment > Fuel and Payload'''
*'''Checklist''' - Displays aircraft checklist '''Help > '''
*'''Failures''' -
*'''Panel''' -
*'''Select''' - ''Known bug in FG for windows versions 7+, assume this feature to not work anytime soon even if you see a list of planes to install''
=== Environment===
*'''Date & Time''' - Change in-sim time of day and current date
*'''Weather''' -
*'''Position''' - Interface where you can search for airports via ICAO codes and then select a runway/parking spot to load into FlightGear '''Location > Select Airport'''
=== Map ===
Loads an OpenStreetMap as the background and updates your current position around the world in real time while you fly. Allows one to not only track current flight, but the ability to drag the plane icon around the map which will instantly update FlightGear with the new lon. and lat. coordinate position.
=== Tools===
Things that make for a more realistic experience. Not exactly needed to fly a plane, but these tools will add to the realism.
*'''Holding Pattern''' - A tool to help one understand how to enter the holding pattern. Enter in the Heading and Inbound Track and the diagram will show you visually the Holding pattern.
*'''Wind Calculator''' -
*'''Vertical Navigation (VNAV)''' - ''from my understanding not anytime soon, needs FG integration first''
*'''Stopwatch''' - Self-explanatory
=== Simulator ===
*'''Screenshot''' - Set the time between screen updates. See [[Phi#Screen Shots]]
*'''Properties''' - In-sim property tree, two-way data binding, good for debugging!
*'''Config''' - In-sim config settings
**'''AI''' - Enable/Disable AI
**'''Multi-Player''' - Enter callsign and select which server to connect to on the multi-player network.
*'''Reset''' - Reset the FlightGear Sim
*'''Exit''' - Quit

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
{{Note| This section should be considered unfinished. If you have something to add, please do so}}
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
Here you can find code examples that have been added to the Phi project
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/
The Horizon example is a fat free, stripped down basic idea of a web based instrument for Phi.
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.html
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.js

== Future Development ==
{{Note|Nothing concrete}}
*improve the aircraft specific plugin system to allow special widgets and pages for aircraft (thinking of the shuttle here)
*make layout and theme configurable
*keep settings persistent between sessions
*write a tile renderer to create map tiles from scenery
*better support for touch events
*together with ThorstenR: UI to configure a 3d weather model

== References ==

Phi

2016-03-23T13:06:30Z

Jaxsin: more developer input

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

''Not exactly appropriate for the Phi wiki page, leaving till I find something more relevant''
{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Phi UI Features ==
Phi is at foremost a multi-platform user interface that has two-way data binding with FlightGear via the internal HTTP web server. This allows Phi to be a fully functional user interface that can directly control FlightGear. The following list is a set of features that are currently implemented and working.
=== Aircraft ===
This is where you will find all things related to the currently selected aircraft in-sim, if available.
*'''Help''' - Displays the aircraft help file '''Help > Aircraft Help'''
*'''Mass & Balance''' - Displays aircraft specific fuel and payload options '''Equipment > Fuel and Payload'''
*'''Checklist''' - Displays aircraft checklist '''Help > '''
*'''Failures''' -
*'''Panel''' -
*'''Select''' - ''Known bug in FG for windows versions 7+, assume this feature to not work anytime soon even if you see a list of planes to install''
=== Environment===
*'''Date & Time''' - Change in-sim time of day and current date
*'''Weather''' -
*'''Position''' - Interface where you can search for airports via ICAO codes and then select a runway/parking spot to load into FlightGear '''Location > Select Airport'''
=== Map ===
Loads an OpenStreetMap as the background and updates your current position around the world in real time while you fly. Allows one to not only track current flight, but the ability to drag the plane icon around the map which will instantly update FlightGear with the new lon. and lat. coordinate position.
=== Tools===
Things that make for a more realistic experience. Not exactly needed to fly a plane, but these tools will add to the realism.
*'''Holding Pattern''' - A tool to help one understand how to enter the holding pattern. Enter in the Heading and Inbound Track and the diagram will show you visually the Holding pattern.
*'''Wind Calculator''' -
*'''Vertical Navigation (VNAV)''' - ''from my understanding not anytime soon, needs FG integration first''
*'''Stopwatch''' - Self-explanatory
=== Simulator ===
*'''Screenshot''' - Set the time between screen updates. See [[Phi#Screen Shots]]
*'''Properties''' - In-sim property tree, two-way data binding, good for debugging!
*'''Config''' - In-sim config settings
**'''AI''' - Enable/Disable AI
**'''Multi-Player''' - Enter callsign and select which server to connect to on the multi-player network.
*'''Reset''' - Reset the FlightGear Sim
*'''Exit''' - Quit

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
Here you can find code examples that have been added to the Phi project
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/
The Horizon example is a fat free, stripped down basic idea of a web based instrument for Phi.
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.html
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.js

== References ==

File:FFGo launcher.PNG

2016-03-23T12:23:15Z

Jaxsin: /* {{int:filedesc}} */

=={{int:filedesc}}==
{{Information
|description={{en|1=http daemon option for FG in FFGo launcher}}
|date=2016-03-23
|source={{own}}
|author=[[User:Jaxsin|Jaxsin]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:FFGo screenshots]]

File:FFGo launcher.PNG

2016-03-23T12:22:43Z

Jaxsin: Jaxsin uploaded a new version of File:FFGo launcher.PNG

=={{int:filedesc}}==
{{Information
|description={{en|1=http daemon option for FG in FFGo launcher}}
|date=2016-03-21
|source={{own}}
|author=[[User:Jaxsin|Jaxsin]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:FFGo screenshots]]

Aircraft Center

2016-03-23T00:26:08Z

Jaxsin:

[[Category:Articles containing Instant Cquotes]]
{{Non-stable|progress=50|version=4.x}}

{{Stub}}

[[File:Aircraft-center-prototype.png|400px|thumb|Canvas dialog showing the prototype for an [[Aircraft Center]] for directly downloading/installing/managing -and switching between- aircraft from within FlightGear, an upcoming '''experimental''' feature scheduled for FlightGear 3.2, currently being developed by TheTom and Zakalawe]]

{{cquote
|<nowiki>Recently I've also been mulling the possibility of selecting
aircraft from an "in program" dialog similar to Fly II where you can climb up
to 35,000 feet in a 747 and then switch to a C172 :-) Seriously, even if we
did a full reset, it'd be nice to switch aircraft (3D models as well) and
fdm's on the fly (pun not intended).</nowiki>
|{{cite web |url=http://www.mail-archive.com/flightgear-devel%40flightgear.org/msg09563.html
|title=<nowiki>starting the XML GUI; early implementors needed</nowiki>
|author=<nowiki>David Megginson</nowiki>
|date=<nowiki> Fri, 08 Nov 2002 18:01:41 -0800</nowiki>
}}
}}

{{FGCquote
|As we move forward with FlightGear development and future versions, we will be expanding the "in app" aircraft center. This dialog inside flightgear lets you select, download, and switch to any of the aircraft in the library.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33451055/
|title=<nowiki>Re: [Flightgear-devel] Citation II for base package?</nowiki>
|author=<nowiki>Curtis Olson</nowiki>
|date=<nowiki>2015-02-17</nowiki>
}}
}}

{{FGCquote
|the goal here is to almost get rid of a centralised aircraft repo anyway, and have a decentralised development system with the only central point being the aircraft package manager for end users. Then 99% of people never care where the aircraft is stored while it’s developed.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33413096/
|title=<nowiki>Re: [Flightgear-devel] FGDATA split without Aircraft. Addon in SVN.
(re)Suggesting a Submodule approach. (Re)Proposing a per-Aircraft
repository</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2015-02-13</nowiki>
}}
}}

{{FGCquote
|For all other aircraft, the intention for both these nightly builds and official releases is to use the aircraft catalog + package system, which is based around HTTP rather than an SCM system. I’m working at the moment on integrating the client parts into the launcher GUI.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33586444/
|title=<nowiki>Re: [Flightgear-devel] FGDATA and Jenkins</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2015-03-11</nowiki>
}}
}}
{{Package Management}}
== Background ==
{{Note|Also see [[The FlightGear Front-End Situation]]}}

{{FGCquote
|1= The Canvas-based Aircraft Center dialog was originally prototyped by TheTom in response to Zakalawe announcing on the devel list that he was going to come up with a front-end for his still ongoing package manager subsystem, by creating a hard-coded PUI dialog.
Since then, many things have changed - Zakalawe is now working on an integrated Qt5 launcher, which is intended to remain an optional feature, but which is also intended to provide an in-sim replacement for the built-in PUI GUI.
Also, TheTom is not currently as actively involved as Zakalawe, so that the Aircaft Center has not seen much attention recently - and Zakalawe stated on the devel list that he is now considering the "Aircraft Center" an "experimental feature" that is likely to be deprecated due to this ongoing Qt5 launcher/GUI efforts.
The Aircraft Center is primarily written in Nasal and Canvas, as its back-end it is using SimGear http binding for downloading aircraft, and a few fgcommands for dealing with the package manager subsystem.
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=275645#p275645
| title = <nowiki>Re: Aircraft Center</nowiki>
| author = <nowiki>Hooray</nowiki>
| date = Feb 10th, 2016
| added = Feb 10th, 2016
| script_version = 0.25
}}
}}

Internally, the launcher is implemented in the form of a Nasal script that resides in $FG_ROOT/Nasal/canvas/gui/dialogs/AircraftCenter.nas using the Canvas GUI APIs and a handful of widgets. All the package manager functionality lives in SimGear and is triggered in the form of so called fgcommands. Thus, the list itself will be populated based on XML files that are automatically downloaded. If there are errors related to fetching/using those files, they shoudl show up in $FG_HOME/fgfs.log (look for Catalog.cxx).

The fetched files are to be found in $FG_HOME/Aircraft/org.flightgear.*

{{FGCquote
|The "built-in" GUI/launcher is one of the longest-standing feature requests - but it's not just about the GUI (which is rather straightforward in comparison), but about the simulator never having been developed with this requirement, i.e. run-time reinitialization, in mind - thus, things like "fgrun" (and a plethora of other external launchers) were developed, which acted as a front-end on top of FG, so that FG itself wouldn't need to be changed - i.e. kind of a "remote control" using command line arguments. So it's there for a reason - fgrun uses the FLTK GUI library, which while relatively simple, is much more powerful than our legacy GUI engine, PUI. 
 
Still, people have been asking for this for years, and it's thanks to pretty much a single person, Zakalawe, that switching aircraft is going to become possible pretty soon - he handled all the ugly work of cleaning up the simulator internals to make this happen - it's not exactly glamorous work, you gotta touch a ton of places, and you inevitably introduce a ton of regressions along the way.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213461#p213461
|title=<nowiki>Re: About FlightGear being user-friendly or not</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Thu Jun 26</nowiki>
}}
}}

{{FGCquote
|And yes, even the legacy FG GUI is entirely based on XML and configurable through just editiing XML files - but the collection of "widgets" (GUI controls like buttons, checkboxes, labels etc) is extremely small and very inflexible. 
 
This is something that is currently being addressed by TheTom and Zakalawe, who've both been working on a new Canvas GUI, and a new Canvas GUI dialog called "Aircraft Center", which -while still experimental- is intended to eventually allow end-users to easily download/install aircraft right within the simulator, and also switch between aircraft at run-time without having to exit/restart the simulator. 
 
Thus, adopting Canvas is going to address a number of long-standing issues, but it's obviously a process that only just got started, and it will not happen overnight - 2-3 release cycles are not far-fetched, that's how long the whole migration could very well take, unless there are more people interested in helping.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213461#p213461
|title=<nowiki>Re: About FlightGear being user-friendly or not</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Thu Jun 26</nowiki>
}}
}}

{{FGCquote
|Note that the upcoming FlightGear release is likely to contain an integrated, hard-coded, launcher based on Qt5 to work around this non-working launcher on MacOS: {{flightgear source|commit=f3810707d53f3c04769bbc214036ee9156bc3a7c|file=src/Main/main.cxx}} 
 
Unfortunately, this is -once again- overlapping with other efforts (think [[Canvas GUI]]/[[Aircraft Center]]), and it's going to be Mac specific, too.
If it wasn't for the recent mongoose GUI/Canvas GUI efforts, and had this been done/accepted a few years ago, many recent developments would be made obsolete by allowing Qt5 - but back then, Qt5 was a "no-go"...
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=228961#p228961
|title=<nowiki>Re: FG cannot be opened on new iMac</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sun Jan 04</nowiki>
}}
}}

{{FGCquote
|The Aircraft Center is implemented entirely in scripting space - the package manager is exposed to Nasal via extension functions - it's probably (hopefully) just a matter of adapting 3-5 lines of code to try the other URLs if the first URL fails - for which you'll need to check the error code/state (property tree). please see $FG_ROOT/Nasal/canvas/gui/dialogs/AircraftCenter.nas
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=226929#p226929
|title=<nowiki>Re: Aircraft center: </nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sat Dec 13</nowiki>
}}
}}

== Global Canvas GUI (WIP) ==

{{FGCquote
|we could certainly prepare the main binary to become increasingly configurable, so that it can be used for such purposes - it would even be possible to use built-in FG dialogs in an external window, running in a standalone process - e.g. for an instructor console, but also for a Canvas-driven TerraGear GUI.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214286#p214286
|title=<nowiki>Re: How can I retire from the forum?</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Mon Jul 07</nowiki>
}}
}}

{{FGCquote
|(This subject has been discussed at FSWeekend) 
 
I'm slowly working on a new "global" GUI created in Canvas. It's still in heavy development and I'm not sure I will have time to finish it for FG 3.4, but if people are helping I think we can get it.
[[File:Canvas-gui-experiments-by-F-JJTH-1.png|thumb|Canvas GUI experiments by F-JJTH (11/2014) [http://sourceforge.net/p/flightgear/mailman/message/33053113/]]]
[[File:Canvas-gui-experiments-by-F-JJTH-2.png|thumb|Canvas GUI experiments by F-JJTH (11/2014) [http://sourceforge.net/p/flightgear/mailman/message/33053113/]]]
[[File:Canvas-gui-experiments-by-F-JJTH-3.png|thumb|Canvas GUI experiments by F-JJTH (11/2014) [http://sourceforge.net/p/flightgear/mailman/message/33053113/]]]
[[File:Canvas-gui-experiments-by-F-JJTH-4.png|thumb|Canvas GUI experiments by F-JJTH (11/2014) [http://sourceforge.net/p/flightgear/mailman/message/33053113/]]]
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33053113/
|title=<nowiki>Re: [Flightgear-devel] Features for 3.4 please</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-11-18</nowiki>
}}
}}

{{FGCquote
|The goal is to replace our dozens of GUI dialog by only 1 dialog with nice architecture/organization. 
For example, the "General" page is remplacing "File > Sound configuration", "View > Cockpit View Options", "View > Adjust HUD Properties" and "View > View Options".
Some Canvas tools are missing (slider, radio button, styling helper like "font-bold", "underline"...) but I know Canvas is under development.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33053113/
|title=<nowiki>Re: [Flightgear-devel] Features for 3.4 please</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-11-18</nowiki>
}}
}}

{{FGCquote
|The "Home" page is designed to be the "select airport", "select aircraft", "help"... finally this dialog could become the "built-in launcher".For
example we can imagine to have an option like --enable-launcher which start FG in a way that he doesn't load any aircraft or position but
instead we hold the splashscreen and we show this Canvas dialog, then the user can select his airport and his aircraft. Finally a simple
'reset' with all settings required by the user is triggered that way the user end up in his aircraft at his airport.
All of this require to be discussed and is likely at the "proof-of-concept" state.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33053113/
|title=<nowiki>Re: [Flightgear-devel] Features for 3.4 please</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-11-18</nowiki>
}}
}}

{{FGCquote
|Looks … okay, just be aware how it will interact with the menubar. (Especially on Mac). 
 
I actually considered the same, unifying many settings dialogs into one Preferences dialog; not combing ‘everything’ but all the Rendering / View / Multiplayer / Scenery Download / Instrument settings into one Preferences dialog with tabs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33055321/
|title=<nowiki>Re: [Flightgear-devel] Features for 3.4 please</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-11-19</nowiki>
}}
}}

{{FGCquote
|I would still think that a series of top level dialogs might make more sense, based on frequency of use: 
* an aircraft selection / startup location / scenario selection (aka ‘the launcher’) ; something that is shown by default on launch and used every day 
* a preferences + settings + joystick config one which hopefully is not used every day (once things are setup) 
* a help + about dialog which again hopefully is not used every day, maybe designed to remain open on screen
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33055321/
|title=<nowiki>Re: [Flightgear-devel] Features for 3.4 please</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-11-19</nowiki>
}}
}}

{{FGCquote
|I’m not sure how the equipment dialogs (which are often customised per-aircraft - eg radios or autopilot), including the GPS and route-manager, fit into this either.
Of course, it’s great if Canvas is as the point that we can actually consider such things, and hopefully the actual arrangement of screens + widgets is easy to evaluate and adjust.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33055321/
|title=<nowiki>Re: [Flightgear-devel] Features for 3.4 please</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-11-19</nowiki>
}}
}}

== Feature Requests ==
=== Supporting separate/external Windows for the GUI ===
{{FGCquote
|This looks promising in a technical/coding perspective of having this and that common GUI feature available also for flightgear. But for me personally one of the big problems of the FlightGear GUI is that it is "inside" the only and one main window. There is no possibility to have a separate window to not cover the main content, the scenery and the cockpit? This would make the GUI much more practical. I would really like to run flightgear with one window "view" and other windows for the program (options). This will improve the usability of all the menus, dialogs etc. a lot in my opinion.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/29586327/
|title=<nowiki>Re: [Flightgear-devel] Switching from PUI to osgWidget</nowiki>
|author=<nowiki>ys</nowiki>
|date=<nowiki>2012-07-24</nowiki>
}}
}}

== Status ==
{{cquote
|I've pushed now a first version of an aircraft install/removal dialog. 
Was a lot more effort than expected, but now there are a lot of 
improvements available useful for every type of dialog.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32441965/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>Thomas Geymayer</nowiki>
|date=<nowiki>2014-06-10</nowiki>
}}
}}

{{cquote
|The dialog is available in the menu (File > Aircraft Center) and shows 
a list of the 100 first aircrafts available to install/remove. I've 
chosen to limit the number, because with showing all aircrafts at once 
I got a delay of a few seconds on opening the dialog. I will 
investigate into this more later. You can use the according buttons to 
install/remove aircrafts - which I have already done successfully. 
Currently the dialog does not indicate any progress and needs to be 
reopened to update the buttons. 
 
As the feature freeze is already approaching, I won't be able to add 
too much features for this release. So I think there won't be any 
keyboard input/searching for this release. I want to support different 
tabs to show a list of eg. just the installed aircrafts and do a 
simple cache for all the downloaded images, to have them visible 
faster on opening the dialog.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32441965/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>Thomas Geymayer</nowiki>
|date=<nowiki>2014-06-10</nowiki>
}}
}}

{{cquote
|Thomas Geymayer and I are working on it, I am not sure where’s he go to with the UI, the backend pieces are mostly there but will need some intensive testing. There is a #define flag you can toggle (in HTTPClient.cxx) to enable the code including the Nasal API; it will download / refresh a catalog, which is generated by the scripts I committed to fgmeta a week ago. Then you can access the package system from pkg.root in the Nasal console, using the API defined at the bottom of HTTPClient.cxx. 
 
If you are crazy enough to enable this code, and run it, be aware it downloads zips, unpacks them, makes calls to unlink files, renames directories, and so on. I would recommend some caution, and especially, don’t run it as root - while developing it I had it extract a few zips to ‘/‘ or worse due to screwed up path logic. 
 
Equally, I would welcome a code review of the code in simgear/package/Install.cxx to check any security issues or dangerous behaviour. The code /tries/ to be ‘safe’ - extract zip to a temporary folder, and uses rename/unlink to atomically update if the zip extraction succeeds. But it’s only had one pair of eyes on it so far.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32440549/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-06-10</nowiki>
}}
}}

{{cquote
|My next objective will be actually switching to an aircraft, and setting up the correct paths so that dependencies work; this is more or less orthogonal, I will make a new command to select an aircraft (and reset the sim) based on an aircraft ID or fully-qualified ID. (Again to allow catalogs with ID collisions, such as org.flightgear.default.747-400 and nl.gijs-hangar.beta.747-400) 
 
If anyone wishes to start adding tags or more meta-data to aircraft in FGdata, please let me know, especially to keep the tag space coherent and hence useful for searching.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32443649/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-06-10</nowiki>
}}
}}

{{cquote
|the whole thing is still pretty experimental, it’s probably not at the ‘this text should be a little to the left’ point. We’re more at the ‘it didn’t erase your C drive? Great!’ stage….
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32457767/
|title=<nowiki>Re: [Flightgear-devel] Notes on Aircraft Center...</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-06-13</nowiki>
}}
}}

{{cquote
|The layout and widget systems is now maturing, so I think after 3.2 I 
can start with porting PUI. Just one major component is missing, namely 
keyboard input and the according input focus. 
 
I guess this will take one or two more releases.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32457866/
|title=<nowiki>Re: [Flightgear-devel] Notes on Aircraft Center...</nowiki>
|author=<nowiki>Thomas Geymayer</nowiki>
|date=<nowiki>2014-06-13</nowiki>
}}
}}

== Tagging ==
{{cquote
|Related to this, does anyone know how standardised the <status> values are? If there is a defined list of values I will add query support and expose them as an enum to Nasal. 
 
And, if anyone who has a custom hangar would like to start maintaining a catalog, please let me know - there is no UI in FG to add additional catalogs yet but it would help with testing. If you already have a web server with zip files of aircraft, you only need to serve one extra XML file to run a ‘package-ified’ hangar. The catalog XML can be hand written or generated using any technology you like - there’s Python scripts in fgmeta, but PHP / shell-script / etc will all work too.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32445402/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-06-11</nowiki>
}}
}}

{{cquote
| have updated my script with to restrict tags to the set I original wrote on the wiki some time ago: 
 
http://wiki.flightgear.org/Catalog_metadata 
 
I am going to do make a drive-by assault on fgdata/Aircraft adding tags - hopefully no maintainer feels this is problematic since it’s purely adding metadata to make the UI more functional. I am sure I will get some entries ‘wrong’ and the tags themselves are still up for discussion, but we have a version control system, and most of the tags are very non-controversial. 
 
The ‘nicer’ Nasal tags syntax is added now too. (Part of the motivation for adding tags to fgdata is to test it better( 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32451527/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-06-12</nowiki>
}}
}}

== Variants ==
{{cquote
| I don’t think there’s any pathological examples with more than eight -set.xml. Designating the ‘main’ -set.xml is still an issue. 
 
What I will do is include the set-file and description in a ‘variants’ list, with the first entry being the default. So in the catalog XML, something like: 
 
<package> 
<variant> 
<id>747-400-FO</id> 
<name>747-400 First-officer mode</name> 
</variant> 
... 
</package> 
 
On Package I’ll expose this as string_list of variants() with a nameForVariant(std::string variant) helper. For Nasal I can return a dictionary. 
 
Variant IDs will need to be unique within the Catalog, and I’ll update the search logic to accept /any/ variant ID as matching the package - this will make the aircraft-startup part of everything work, and keeps thing close to how it behaves with unpackaged aircraft.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32457202/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-06-13</nowiki>
}}
}}

Aircraft developers can make use of a new tag in the [[Aircraft-set.xml]] file. Added to the <code><nowiki><sim></nowiki></code>, the <code><nowiki><variant-of></nowiki></code> tag states to the launcher the aircraft type that your aircraft is a variant of. For example, the [[British Aerospace Sea Harrier|BAe Sea Harrier FA2]] is a variant of the BAe Sea Harrier, and the ''Cessna 172P - Canvas Demo'' is a variant of the [[Cessna C172P|C172P]].

{{note|At the moment, only the Mac Qt launcher (which comes with FlightGear for Mac v3.4+) will read this tag.}}

Syntax:
<syntaxhighlight lang="xml">
<sim>
...
<variant-of>[aircraft]</variant-of>
...
</sim>
</syntaxhighlight>

Example from {{repo link|site=gito|path=Aircraft/777/777-200ER-set.xml|pre=$FG_ROOT}} (see {{gitorious source|proj=fg|repo=fgdata|commit=1017a32b1b078f46959b3b6e7510a7376458b02b|view=commit}}):

<code><nowiki><variant-of>777-200</variant-of></nowiki></code>

== Development ==
{{cquote
|I thought about adding a cache add Canvas::Image or rather at the 
HTTPRequest level to cache all HTTP requests/files which have not set 
a no-cache header.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32442349/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>Thomas Geymayer</nowiki>
|date=<nowiki>2014-06-10</nowiki>
}}
}}

{{cquote
| for a first step I want to limit it only to the 
HTTPMemoryRequest which is mainly used for downloading canvas images. So 
it should not affect too many parts. 
Someday we should probably add a cache limit - but not now ;-) I will 
also need this for displaying tilemaps.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32443509/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>Thomas Geymayer</nowiki>
|date=<nowiki>2014-06-10</nowiki>
}}
}}

{{cquote
|A semi-related small thing: I'd like to have saved-between-sessions 
"default aircraft/starting airport" properties (/sim/default-aircraft, 
/sim/default-airport ?), set by a "make this default" check box in Go To 
Airport and the new aircraft dialog, so those who prefer something other 
than c172p@... don't have to select it on every startup. I should be 
able to implement this, but comments would be appreciated.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32398014/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>Rebecca N. Palmer</nowiki>
|date=<nowiki>2014-05-30</nowiki>
}}
}}

{{cquote
|Currently box layouts are available. Once they fully 
work I'll start thinking of other layouts and widgets.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32457866/
|title=<nowiki>Re: [Flightgear-devel] Notes on Aircraft Center...</nowiki>
|author=<nowiki>Thomas Geymayer</nowiki>
|date=<nowiki>2014-06-13</nowiki>
}}
}}

{{cquote
|I want 
to implement a cache to speed it up after the first time, but not for 
3.2. If an image fails to load there should be a message in the terminal. 
"No thumbnail available" is shown if there is no image specified in the 
catalog.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32457866/
|title=<nowiki>Re: [Flightgear-devel] Notes on Aircraft Center...</nowiki>
|author=<nowiki>Thomas Geymayer</nowiki>
|date=<nowiki>2014-06-13</nowiki>
}}
}}

{{cquote
|what I’d want is tabs at the top for ‘installed aircraft’, ‘available updates’ and so on. But again the question is really what UI we can build in the time available.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32457767/
|title=<nowiki>Re: [Flightgear-devel] Notes on Aircraft Center...</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-06-13</nowiki>
}}
}}

== Known Issues ==
{{FGCquote
|The default aircraft catalog download path is http://fgfs.goneabitbursar.com/pkg/<version>/default-catalog.xml, which does not exist for 3.4.0 or 3.5.0, giving a "catalog download failure:" error and an empty Aircraft Center.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33679386/
|title=<nowiki>[Flightgear-devel] Non-existent default catalog</nowiki>
|author=<nowiki>Rebecca N. Palmer</nowiki>
|date=<nowiki>2015-03-31</nowiki>
}}
}}

{{FGCquote
|Also, the address includes the micro version: is that intentional or not? catalog download failure:http://fgfs.goneabitbursar.com/pkg/3.4.1/default-catalog.xml
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33679621/
|title=<nowiki>Re: [Flightgear-devel] Non-existent default catalog</nowiki>
|author=<nowiki>Rebecca N. Palmer</nowiki>
|date=<nowiki>2015-03-31</nowiki>
}}
}}

{{FGCquote
|It would be good to resolve the missing aircraft center database.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33681336/
|title=<nowiki>Re: [Flightgear-devel] fgdata 3.4.1</nowiki>
|author=<nowiki>Curtis Olson</nowiki>
|date=<nowiki>2015-03-31</nowiki>
}}
}}

{{cquote
|Prior to a reset, if you edit /sim/aircraft, it works as you would expect. However there are some quirks related to aircraft-specific menu items / dialogs, at least on Mac (the custom menu for previous aircraft is not removed). 
 
There may be other bugs, since this feature is not used by anyone yet.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32397779/
|title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-05-30</nowiki>
}}
}}

{{cquote
|If you've created a grid control for Canvas, it would be nice to see the 
FDM, Systems, Cockpit and Model ratings broken out into individual columns 
so you could sort by them. :) 
 
If you get to the point where you can change aircraft from this dialog, 
you might want to include a checkbox that will limit the list to installed 
aircraft. 
 
If the Aircraft Center dialog is open, other dialogs don't appear to work 
- I tried exiting via File->Exit and none of the items were selectable. 
Hitting ESC brings up the Exit dialog, but the buttons were not clickable. 
 
Dismissing the Aircraft Center dialog allowed the other dialogs to operate 
properly.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32457611/
|title=<nowiki>[Flightgear-devel] Notes on Aircraft Center...</nowiki>
|author=<nowiki>geneb</nowiki>
|date=<nowiki>2014-06-13</nowiki>
}}
}}

{{cquote
|The Canvas fonts are blurry compared to the in.sim Menu bar Fonts -Richi Muchacho
}}

Phi

2016-03-22T13:20:30Z

Jaxsin: /* Phi - 'map in browser' */

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

''Not exactly appropriate for the Phi wiki page, leaving till I find something more relevant''
{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Phi UI Features ==
Phi is at foremost a multi-platform user interface that has two-way data binding with FlightGear via the internal HTTP web server. This allows Phi to be a fully functional user interface that can directly control FlightGear. The following list is a set of features that are currently implemented and working.
=== Aircraft ===
This is where you will find all things related to the currently selected aircraft in-sim, if available.
*'''Help''' - Displays the aircraft help file '''Help > Aircraft Help'''
*'''Mass & Balance''' - Displays aircraft specific fuel and payload options '''Equipment > Fuel and Payload'''
*'''Checklist''' - Displays aircraft checklist '''Help > '''
*'''Failures''' -
*'''Panel''' -
*'''Select''' - ''Known bug in FG for windows versions 7+, assume this feature to not work anytime soon even if you see a list of planes to install''
=== Environment===
*'''Date & Time''' - Change in-sim time of day and current date
*'''Weather''' -
*'''Position''' - Interface where you can search for airports via ICAO codes and then select a runway/parking spot to load into FlightGear '''Location > Select Airport'''
=== Map ===
Loads an OpenStreetMap as the background and updates your current position around the world in real time while you fly. Allows one to not only track current flight, but the ability to drag the plane icon around the map which will instantly update FlightGear with the new lon. and lat. coordinate position.
=== Tools===
Things that make for a more realistic experience. Not exactly needed to fly a plane, but these tools will add to the realism.
*'''Holding Pattern''' - A tool to help one understand how to enter the holding pattern. Enter in the Heading and Inbound Track and the diagram will show you visually the Holding pattern.
*'''Wind Calculator''' -
*'''Vertical Navigation (VNAV)''' - ''from my understanding not anytime soon, needs FG integration first''
*'''Stopwatch''' - Self-explanatory
=== Simulator ===
*'''Screenshot''' - Set the time between screen updates. See [[Phi#Screen Shots]]
*'''Properties''' - In-sim property tree, two-way data binding, good for debugging!
*'''Config''' - In-sim config settings
**'''AI''' - Enable/Disable AI
**'''Multi-Player''' - Enter callsign and select which server to connect to on the multi-player network.
*'''Reset''' - Reset the FlightGear Sim
*'''Exit''' - Quit

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
'''Open the SVG file in inkscape and enter the xml editor (Ctrl + shift + X) to view the data-bind attributes for the objects that need animating'''
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.svg
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.js

== References ==

Phi

2016-03-22T13:06:44Z

Jaxsin: Updates based on developers input

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

''Not exactly appropriate for the Phi wiki page, leaving till I find something more relevant''
{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Phi UI Features ==
Phi is at foremost a multi-platform user interface that has two-way data binding with FlightGear via the internal HTTP web server. This allows Phi to be a fully functional user interface that can directly control FlightGear. The following list is a set of features that are currently implemented and working.
=== Aircraft ===
This is where you will find all things related to the currently selected aircraft in-sim, if available.
*'''Help''' - Displays the aircraft help file '''Help > Aircraft Help'''
*'''Mass & Balance''' - Displays aircraft specific fuel and payload options '''Equipment > Fuel and Payload'''
*'''Checklist''' - Displays aircraft checklist '''Help > '''
*'''Failures''' -
*'''Panel''' -
*'''Select''' - ''Known bug in FG for windows versions 7+, assume this feature to not work anytime soon even if you see a list of planes to install''
=== Environment===
*'''Date & Time''' - Change in-sim time of day and current date
*'''Weather''' -
*'''Position''' - Interface where you can search for airports via ICAO codes and then select a runway/parking spot to load into FlightGear '''Location > Select Airport'''
=== Map ===
Loads an OpenStreetMap as the background and updates your current position around the world in real time while you fly. Allows one to not only track current flight, but the ability to drag the plane icon around the map which will instantly update FlightGear with the new lon. and lat. coordinate position.
=== Tools===
Things that make for a more realistic experience. Not exactly needed to fly a plane, but these tools will add to the realism.
*'''Holding Pattern''' - A tool to help one understand how to enter the holding pattern. Enter in the Heading and Inbound Track and the diagram will show you visually the Holding pattern.
*'''Wind Calculator''' -
*'''Vertical Navigation (VNAV)''' - ''from my understanding not anytime soon, needs FG integration first''
*'''Stopwatch''' - Self-explanatory
=== Simulator ===
*'''Screenshot''' - Set the time between screen updates. See [[Phi#Screen Shots]]
*'''Properties''' - In-sim property tree, two-way data binding, good for debugging!
*'''Config''' - In-sim config settings
**'''AI''' - Enable/Disable AI
**'''Multi-Player''' - Enter callsign and select which server to connect to on the multi-player network.
*'''Reset''' - Reset the FlightGear Sim
*'''Exit''' - Quit

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
'''Open the SVG file in inkscape and enter the xml editor (Ctrl + shift + X) to view the data-bind attributes for the objects that need animating'''
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.svg
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.js

== References ==

Phi

2016-03-22T01:32:19Z

Jaxsin:

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
'''Open the SVG file in inkscape and enter the xml editor (Ctrl + shift + X) to view the data-bind attributes for the objects that need animating'''
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.svg
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.js

== References ==

Phi

2016-03-22T01:29:36Z

Jaxsin: /* Web-based EFIS */

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
'''Open the SVG file in inkscape and enter the xml editor (Ctrl + shift + X) to view the data-bind attributes for the objects that need animating'''
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.svg
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.js

Phi

2016-03-22T01:29:17Z

Jaxsin: /* Examples */

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
'''Open the SVG file in inkscape and enter the xml editor (Ctrl + shift + X) to view the data-bind attributes for the objects that need animating'''
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.svg

https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.js

Phi

2016-03-22T01:27:45Z

Jaxsin: /* Examples */

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
'''Open the SVG file in inkscape and enter the xml editor (Ctrl + shift + X) to view the data-bind attributes for the objects that need animating'''
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.svg

https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.js

Phi

2016-03-22T01:25:51Z

Jaxsin: /* Web-based EFIS */ Added in an example for web-panel instruments

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main article|FFGo}}
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

==== Examples ====
'''Open the SVG file in inkscape and enter the xml editor (Ctrl + shift + X) to view the data-bind attributes for the objects that need animating'''
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.svg
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/widgets/efis.js

Phi

2016-03-22T01:10:12Z

Jaxsin: /* FFGo */

Phi

2016-03-22T01:09:33Z

Jaxsin: /* FFGo */

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
{{Main Article|FFGo}}
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

Phi

2016-03-22T00:35:35Z

Jaxsin:

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

=== Making Web-Panel instruments ===
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

Phi

2016-03-22T00:29:33Z

Jaxsin: Fixed some references and few minor mistakes

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref name="HelloFGP2.0"></ref>

== Making Web-Panel instruments ==
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, 
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.
<ref name="HelloFGP2.0"></ref>

Phi

2016-03-22T00:16:25Z

Jaxsin: Quoting cleanup

{{Note|This article is currently in the process of being updated/rewritten by {{Usr|Jaxsin}}}}
[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref>

Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:

{{#ev:youtube|sYM7uiWIprc}}

You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref>

== Usage ==
==== Qt5 Launcher ====
{{Main article|Integrated Qt5 Launcher}}
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>

The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent git has all it needs. Workload for FlightGear is neglible, for the current EFIS, on page load a few hundret kilobyte of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.
<ref>[[HelloFGP2.0]]</ref>

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T20:27:59Z

Jaxsin: /* Screen Shots */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:

*'''type:''' either png or jpg (guess what this does)

*'''window:''' the name of the window to capture (for those with multi screen setups)

*'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Force Feedback Support in FlightGear

2016-03-21T20:06:14Z

Jaxsin:

See [[Force_feedback]]

Force Feedback Support in FlightGear

2016-03-21T20:03:04Z

Jaxsin: Quoting cleanup - No merge needed, Zan has the force feedback wiki in good order

Phi

2016-03-21T19:35:56Z

Jaxsin: /* Background */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:
'''type:''' either png or jpg (guess what this does)
'''window:''' the name of the window to capture (for those with multi screen
setups)
'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T19:30:34Z

Jaxsin: /* Screen Shots */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:
'''type:''' either png or jpg (guess what this does)
'''window:''' the name of the window to capture (for those with multi screen
setups)
'''stream:''' provide mjpeg stream

===Examples:===
==== Single screenshot ====
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
==== Motion-jpeg ====
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T19:29:28Z

Jaxsin: /* Screen Shots */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:
'''type:''' either png or jpg (guess what this does)
'''window:''' the name of the window to capture (for those with multi screen
setups)
'''stream:''' provide mjpeg stream

Examples:
=== Single screenshot ===
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
=== Motion-jpeg ===
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T19:27:11Z

Jaxsin: /* Screen Shots */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:
'''type:''' either png or jpg (guess what this does)
'''window:''' the name of the window to capture (for those with multi screen
setups)
'''stream:''' provide mjpeg stream

Examples:
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA
Send a motion-jpeg encoded video stream.
http://localhost:8080/screenshot?window=WindowA&stream=y
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T19:26:26Z

Jaxsin: Quoting cleanup

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]]
http://localhost:8080/screenshot

It understands some request parameters:
'''type:''' either png or jpg (guess what this does)
'''window:''' the name of the window to capture (for those with multi screen
setups)
'''stream:''' provide mjpeg stream

Examples:
send png instead of jpg (jpg is default)
http://localhost:8080/screenshot?type=png
send a png screenshot from the window named "WindowA" as defined under
rendering/camera-group/window/name in your screen configuration.
http://localhost:8080/screenshot?type=png&window=WindowA
use default jpg encoding
http://localhost:8080/screenshot?window=WindowA

http://localhost:8080/screenshot?window=WindowA&stream=y
Send a motion-jpeg encoded video stream.
Can be used by ffmpeg to directly encode various video formats.
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y

Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T19:15:33Z

Jaxsin: /* FFGo */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file. Please visit [[FFGo]] for further details

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
{{FGCquote
|You can access the new screenshot handler after starting with 
--httpd{{=}}8080 at http://localhost:8080/screenshot 
 
It understands some request parameters: 
type: either png or jpg (guess what this does) 
window: the name of the window to capture (for those with multi screen 
setups) 
stream: provide mjpeg stream
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}
{{FGCquote
|Examples: 
 
http://localhost:8080/screenshot?type=png 
send png instead of jpg (jpg is default) 
 
http://localhost:8080/screenshot?type{{=}}png&window{{=}}WindowA 
send a png screenshot from the window named "WindowA" as defined under 
rendering/camera-group/window/name in your screen configuration. 
 
http://localhost:8080/screenshot?window{{=}}WindowA 
do the same as before, but use default jpg encoding
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

{{FGCquote
|http://localhost:8080/screenshot?window{{=}}WindowA&stream{{=}}y 
same as before, but not just send a single image but a motion-jpeg 
encoded video stream. 
Can be used by ffmpeg to directly encode various video formats. 
try ffplay -f mjpeg http://localhost:8080/screenshot/stream{{=}}y 
 
Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY 
hardcoded to 80. 
These seem to be a good balance of performance vs. quality.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T19:05:56Z

Jaxsin: /* Background */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
{{FGCquote
|You can access the new screenshot handler after starting with 
--httpd{{=}}8080 at http://localhost:8080/screenshot 
 
It understands some request parameters: 
type: either png or jpg (guess what this does) 
window: the name of the window to capture (for those with multi screen 
setups) 
stream: provide mjpeg stream
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}
{{FGCquote
|Examples: 
 
http://localhost:8080/screenshot?type=png 
send png instead of jpg (jpg is default) 
 
http://localhost:8080/screenshot?type{{=}}png&window{{=}}WindowA 
send a png screenshot from the window named "WindowA" as defined under 
rendering/camera-group/window/name in your screen configuration. 
 
http://localhost:8080/screenshot?window{{=}}WindowA 
do the same as before, but use default jpg encoding
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

{{FGCquote
|http://localhost:8080/screenshot?window{{=}}WindowA&stream{{=}}y 
same as before, but not just send a single image but a motion-jpeg 
encoded video stream. 
Can be used by ffmpeg to directly encode various video formats. 
try ffplay -f mjpeg http://localhost:8080/screenshot/stream{{=}}y 
 
Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY 
hardcoded to 80. 
These seem to be a good balance of performance vs. quality.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T19:04:14Z

Jaxsin: /* Console */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

FI = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd Example.
fgfs --httpd=8080

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL
http://localhost:8080

== Screen Shots ==
{{FGCquote
|You can access the new screenshot handler after starting with 
--httpd{{=}}8080 at http://localhost:8080/screenshot 
 
It understands some request parameters: 
type: either png or jpg (guess what this does) 
window: the name of the window to capture (for those with multi screen 
setups) 
stream: provide mjpeg stream
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}
{{FGCquote
|Examples: 
 
http://localhost:8080/screenshot?type=png 
send png instead of jpg (jpg is default) 
 
http://localhost:8080/screenshot?type{{=}}png&window{{=}}WindowA 
send a png screenshot from the window named "WindowA" as defined under 
rendering/camera-group/window/name in your screen configuration. 
 
http://localhost:8080/screenshot?window{{=}}WindowA 
do the same as before, but use default jpg encoding
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

{{FGCquote
|http://localhost:8080/screenshot?window{{=}}WindowA&stream{{=}}y 
same as before, but not just send a single image but a motion-jpeg 
encoded video stream. 
Can be used by ffmpeg to directly encode various video formats. 
try ffplay -f mjpeg http://localhost:8080/screenshot/stream{{=}}y 
 
Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY 
hardcoded to 80. 
These seem to be a good balance of performance vs. quality.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T19:01:43Z

Jaxsin: /* FFGo */ added image

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

FI = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd command switch somewhere in the config file.

[[File:FFGo launcher.PNG|300px|FFGo launcher]]

==== Console ====
run fgfs with the command line switch --httpd=8080
*insert image

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. Select Equipment > Map (opens in browser) or launch a web browser and enter the url http://localhost:8080 and press enter.

== Screen Shots ==
{{FGCquote
|You can access the new screenshot handler after starting with 
--httpd{{=}}8080 at http://localhost:8080/screenshot 
 
It understands some request parameters: 
type: either png or jpg (guess what this does) 
window: the name of the window to capture (for those with multi screen 
setups) 
stream: provide mjpeg stream
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}
{{FGCquote
|Examples: 
 
http://localhost:8080/screenshot?type=png 
send png instead of jpg (jpg is default) 
 
http://localhost:8080/screenshot?type{{=}}png&window{{=}}WindowA 
send a png screenshot from the window named "WindowA" as defined under 
rendering/camera-group/window/name in your screen configuration. 
 
http://localhost:8080/screenshot?window{{=}}WindowA 
do the same as before, but use default jpg encoding
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

{{FGCquote
|http://localhost:8080/screenshot?window{{=}}WindowA&stream{{=}}y 
same as before, but not just send a single image but a motion-jpeg 
encoded video stream. 
Can be used by ffmpeg to directly encode various video formats. 
try ffplay -f mjpeg http://localhost:8080/screenshot/stream{{=}}y 
 
Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY 
hardcoded to 80. 
These seem to be a good balance of performance vs. quality.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

File:FFGo launcher.PNG

2016-03-21T19:00:52Z

Jaxsin: User created page with UploadWizard

Phi

2016-03-21T18:13:35Z

Jaxsin: /* Qt5 Launcher */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

FI = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.

[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]

==== FFGo ====
Add the --httpd=8080 command switch end of the config file.
*insert image
==== Console ====
run fgfs with the command line switch --httpd=8080
*insert image

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. Select Equipment > Map (opens in browser) or launch a web browser and enter the url http://localhost:8080 and press enter.

== Screen Shots ==
{{FGCquote
|You can access the new screenshot handler after starting with 
--httpd{{=}}8080 at http://localhost:8080/screenshot 
 
It understands some request parameters: 
type: either png or jpg (guess what this does) 
window: the name of the window to capture (for those with multi screen 
setups) 
stream: provide mjpeg stream
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}
{{FGCquote
|Examples: 
 
http://localhost:8080/screenshot?type=png 
send png instead of jpg (jpg is default) 
 
http://localhost:8080/screenshot?type{{=}}png&window{{=}}WindowA 
send a png screenshot from the window named "WindowA" as defined under 
rendering/camera-group/window/name in your screen configuration. 
 
http://localhost:8080/screenshot?window{{=}}WindowA 
do the same as before, but use default jpg encoding
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

{{FGCquote
|http://localhost:8080/screenshot?window{{=}}WindowA&stream{{=}}y 
same as before, but not just send a single image but a motion-jpeg 
encoded video stream. 
Can be used by ffmpeg to directly encode various video formats. 
try ffplay -f mjpeg http://localhost:8080/screenshot/stream{{=}}y 
 
Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY 
hardcoded to 80. 
These seem to be a good balance of performance vs. quality.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T18:08:27Z

Jaxsin: /* Background */

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]]</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]]</ref>

FI = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.
[[File:Phi launcher option.PNG|thumb|Qt5 launcher option for Phi]]
==== FFGo ====
Add the --httpd=8080 command switch end of the config file.
*insert image
==== Console ====
run fgfs with the command line switch --httpd=8080
*insert image

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. Select Equipment > Map (opens in browser) or launch a web browser and enter the url http://localhost:8080 and press enter.

== Screen Shots ==
{{FGCquote
|You can access the new screenshot handler after starting with 
--httpd{{=}}8080 at http://localhost:8080/screenshot 
 
It understands some request parameters: 
type: either png or jpg (guess what this does) 
window: the name of the window to capture (for those with multi screen 
setups) 
stream: provide mjpeg stream
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}
{{FGCquote
|Examples: 
 
http://localhost:8080/screenshot?type=png 
send png instead of jpg (jpg is default) 
 
http://localhost:8080/screenshot?type{{=}}png&window{{=}}WindowA 
send a png screenshot from the window named "WindowA" as defined under 
rendering/camera-group/window/name in your screen configuration. 
 
http://localhost:8080/screenshot?window{{=}}WindowA 
do the same as before, but use default jpg encoding
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

{{FGCquote
|http://localhost:8080/screenshot?window{{=}}WindowA&stream{{=}}y 
same as before, but not just send a single image but a motion-jpeg 
encoded video stream. 
Can be used by ffmpeg to directly encode various video formats. 
try ffplay -f mjpeg http://localhost:8080/screenshot/stream{{=}}y 
 
Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY 
hardcoded to 80. 
These seem to be a good balance of performance vs. quality.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

Phi

2016-03-21T18:05:58Z

Jaxsin: moved to background section

[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]

== Phi - 'map in browser' ==

'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a web browser or web app's like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.

== Background ==

While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.
<ref>http://sourceforge.net/p/flightgear/mailman/message/32068663/</ref>

Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc 
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript
<ref>http://sourceforge.net/p/flightgear/mailman/message/32840980/</ref>

FI = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter
Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched
from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out http://en.wikipedia.org/wiki/Phi and pick the
one that suits best ;-)
<ref></ref>

== Usage ==
==== Qt5 Launcher ====
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.
[[File:Phi launcher option.PNG|thumb|Qt5 launcher option for Phi]]
==== FFGo ====
Add the --httpd=8080 command switch end of the config file.
*insert image
==== Console ====
run fgfs with the command line switch --httpd=8080
*insert image

Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. Select Equipment > Map (opens in browser) or launch a web browser and enter the url http://localhost:8080 and press enter.

== Screen Shots ==
{{FGCquote
|You can access the new screenshot handler after starting with 
--httpd{{=}}8080 at http://localhost:8080/screenshot 
 
It understands some request parameters: 
type: either png or jpg (guess what this does) 
window: the name of the window to capture (for those with multi screen 
setups) 
stream: provide mjpeg stream
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}
{{FGCquote
|Examples: 
 
http://localhost:8080/screenshot?type=png 
send png instead of jpg (jpg is default) 
 
http://localhost:8080/screenshot?type{{=}}png&window{{=}}WindowA 
send a png screenshot from the window named "WindowA" as defined under 
rendering/camera-group/window/name in your screen configuration. 
 
http://localhost:8080/screenshot?window{{=}}WindowA 
do the same as before, but use default jpg encoding
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

{{FGCquote
|http://localhost:8080/screenshot?window{{=}}WindowA&stream{{=}}y 
same as before, but not just send a single image but a motion-jpeg 
encoded video stream. 
Can be used by ffmpeg to directly encode various video formats. 
try ffplay -f mjpeg http://localhost:8080/screenshot/stream{{=}}y 
 
Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY 
hardcoded to 80. 
These seem to be a good balance of performance vs. quality.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32889510/
|title=<nowiki>[Flightgear-devel] Heads up: --jpg-httpd is gone</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-10-02</nowiki>
}}
}}

== Web-based EFIS ==
{{FGCquote
|I have made some improvement and created a basic JavaScript API. 
 
First victim of my work is the SenecaII. 
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080 
 
Select "Panel in a browser" from the "Seneca" menuentry in the menubar. 
A browser should pop up, showing the Airspeed indicator after a short 
loading-delay. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-18</nowiki>
}}
}}
{{FGCquote
|for a long time, I have been dreaming of a cross-platform, simple 
solution to render 2d panels on a remote device. 
 
I have just succeeded with my first partial implementation of a EFIS PFD 
rendered in a web browser using nothing but existing web standards and a 
running FlightGear instance having the internal web server enabled.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The EFIS is created from scalable vector graphics (svg), is animated by 
JavaScript and driven by properties from FlightGear over websockets. 
The same svg files that are used for the FlightGear internal canvas 
based instruments can also be used for the browser based display, so 
both instruments (that of the 3d model and that in your browser) look 
100% alike. Websocket properties are exchanged at frame rate making 
animations as smooth as they can get. Because it uses SVG, instruments 
are always rendered at the highest available resolution of the device 
without scaling artefacts. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|The most exciting part is, the web based instrument runs on any modern 
platform without the need to install any spooky software. See a 
screenshot of the EFIS rendered on my iPad. 
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0 
It also runs flawless on my Android phone and tablet and of course in a 
standard browser (Firefox and Chrome tested). On mobile OSes, you can 
add it to your home screen, making this a full-screen web-app to get rid 
of the browser navigation and toolbar (like shown in the screenshot). 
 
There is not much required on the FlightGear side - recent git has all 
it needs. Workload for FlightGear is neglible, for the current EFIS, on 
page load a few hundret kilobyte of static files are transmitted and 
once fully loaded, 10 (ten!) properties are observed and transmitted on 
change. All the rendering takes place on the web browser's device.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

{{FGCquote
|If you want to give it a try, make sure you have fg and fgdata from 
latest git HEAD. 
Clone my ZivkoEdge repository from 
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your 
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" 
menu item. 
 
As always: feedback is welcome.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32840486/
|title=<nowiki>[Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-17</nowiki>
}}
}}

== EFIS via SVG ==
{{FGCquote
|I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those. 
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element. 
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far. 
 
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}

{{FGCquote
|Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance. 
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable. 
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32854893/
|title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-22</nowiki>
}}
}}