20,741
edits
Canvas EFB framework: Difference between revisions
Jump to navigation
Jump to search
→Background
m (→Procedural Charts: it works ! - good job @bigstones !) |
|||
| Line 26: | Line 26: | ||
{{Template:Canvas Navigation}} | {{Template:Canvas Navigation}} | ||
== Canvas & PDF == | |||
{{FGCquote | |||
|Looking at the Boeing 777 EFB (which is driven by a Jeppesen Application based on Windows), they use PDF files (in hi-res) for Navigation Charts (and for Aerodromes too, I presume) in order to avoid any zooming problem.<br/> | |||
I'd assume that a hi-res .pdf file would be the best easy solution, at the moment (it will take some time to define an acceptable ''standard'' for procedural charts, I presume): is Canvas capable of displaying a .pdf file? | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213157#p213157 | |||
|title=<nowiki>Re: 777 EFB: initial feedback</nowiki> | |||
|author=<nowiki>I-NEMO</nowiki> | |||
|date=<nowiki>Sun Jun 22</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | |||
|as I mentioned previously, Canvas cannot currently deal with PDF files directly - even though OSG does have support for doing this kind of thing, but we would need to add a few dependencies, i.e. a PDF rendering library like "poppler" that would render a PDF to an osg::Image. At that point, it could be dealt with like a conventional canvas image, and could even be retrieved via HTTP. Extending Canvas accordingly could actually be useful, because it would even allow us to render other PDFs inside dialogs - such as for example the manual itself, i.e. as part of some kind of integrated "help" system. The question is if TheTom can be convinced that this is a worthwhile goal or not. But it's clearly something for post 3.2 <br/> | |||
<br/> | |||
Based on Tom's previous comments, he doesn't really favor procecural chart generation either, but would prefer having some kind of "web service" from which charts etc could be fetched.<br/> | |||
<br/> | |||
Not sure if you'd really want to come up with a corresponding "standard" from scratch, it should be easier to support the real thing, i.e. ARINC 424 / [https://www.eurocontrol.int/services/aeronautical-information-exchange-model-phase-3-p-09 AIXM].<br/> | |||
<br/> | |||
Traditionally, there are "CAD" tools for designing terminal procedures, i.e. tools like ArcGIS: [http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName{{=}}An_overview_of_the_Aeronautical_Solution http://webhelp.esri.com/arcgisdesktop/9 ... l_Solution]<br/> | |||
<br/> | |||
Also see this related discussion on the XP forum: [http://forums.x-plane.org/?showtopic{{=}}46676 http://forums.x-plane.org/?showtopic{{=}}46676] | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213159#p213159 | |||
|title=<nowiki>Re: 777 EFB: initial feedback</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sun Jun 22</nowiki> | |||
}} | |||
}} | |||
== Background == | == Background == | ||