Phi: Difference between revisions

2,500 bytes removed ,  22 March 2016
Quoting cleanup
No edit summary
(Quoting cleanup)
Line 72: Line 72:


== Web-based EFIS ==
== Web-based EFIS ==
{{FGCquote
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.
  |I have made some improvement and created a basic JavaScript API.<br/>
<ref name="HelloFGP2.0">[[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]]</ref>
<br/>
First victim of my work is the SenecaII.<br/>
Pull latest fgdata and run fgfs --aircraft{{=}}SenecaII --httpd{{=}}8080<br/>
<br/>
Select "Panel in a browser" from the "Seneca" menuentry in the menubar.<br/>
A browser should pop up, showing the Airspeed indicator after a short <br/>
loading-delay.<br/>


  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846474/
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.
    |title=<nowiki>Re: [Flightgear-devel] Goodbye fgpanel - hello fgpanel 2.0</nowiki>
<ref>[[HelloFGP2.0]]</ref>
    |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 <br/>
solution to render 2d panels on a remote device.<br/>
<br/>
I have just succeeded with my first partial implementation of a EFIS PFD <br/>
rendered in a web browser using nothing but existing web standards and a <br/>
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 <br/>
JavaScript and driven by properties from FlightGear over websockets.<br/>
The same svg files that are used for the FlightGear internal canvas <br/>
based instruments can also be used for the browser based display, so <br/>
both instruments (that of the 3d model and that in your browser) look <br/>
100% alike. Websocket properties are exchanged at frame rate making <br/>
animations as smooth as they can get. Because it uses SVG, instruments <br/>
are always rendered at the highest available resolution of the device <br/>
without scaling artefacts.<br/>
 
  |{{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 <br/>
platform without the need to install any spooky software. See a <br/>
screenshot of the EFIS rendered on my iPad. <br/>
https://www.dropbox.com/s/uo6hu7jeubuy0vn/EFIS.png?dl{{=}}0<br/>
It also runs flawless on my Android phone and tablet and of course in a <br/>
standard browser (Firefox and Chrome tested). On mobile OSes, you can <br/>
add it to your home screen, making this a full-screen web-app to get rid <br/>
of the browser navigation and toolbar (like shown in the screenshot).<br/>
<br/>
There is not much required on the FlightGear side - recent git has all <br/>
it needs. Workload for FlightGear is neglible, for the current EFIS, on <br/>
page load a few hundret kilobyte of static files are transmitted and <br/>
once fully loaded, 10 (ten!) properties are observed and transmitted on <br/>
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 <br/>
latest git HEAD.<br/>
Clone my ZivkoEdge repository from <br/>
git@...:t3r-fg-ac/zivkoedge.git, add the folder to your <br/>
--fg-aircraft option, fire up the Edge and pick "EFIS" from the "EDGE" <br/>
menu item.<br/>
<br/>
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 ==
== EFIS via SVG ==
67

edits