67
edits
Phi: Difference between revisions
Jump to navigation
Jump to search
m
→Background
(moved to background section) |
m (→Background) |
||
| Line 8: | Line 8: | ||
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. | 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> | <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 <br/> | Probably a video is more descriptive, here is a shot of an earlier (incomplete) version: http://youtu.be/sYM7uiWIprc <br/> | ||
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 | 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> | <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 | FI = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken FI sounds like the Greek letter | ||
| Line 18: | Line 18: | ||
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 | 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 ;-) | one that suits best ;-) | ||
<ref></ref> | <ref>[[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]]</ref> | ||
== Usage == | == Usage == | ||