FlightGear Newsletter June 2014: Difference between revisions

Jump to navigation Jump to search
Line 91: Line 91:
   }}
   }}
}}
}}
{{FGCquote
  |Current development ('modernisation' phase) of the '''Boeing 777 Seattle's EFB''' is going on nicely; the code is shorter, more readable and cleaner.<br/>
I have not finished it, yet (I'd say that it's almost 50% done).
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213104#p213104
    |title=<nowiki>Re: 777 EFB: initial feedback</nowiki>
    |author=<nowiki>I-NEMO</nowiki>
    |date=<nowiki>Sat Jun 21</nowiki>
  }}
}}
{{FGCquote
  |At the moment I have a single Canvas group (i.e., ''EFB_group''), with 5 children: the text-matrix (16 left lines, 16 right lines), a Title line , an Helper line and the Display.<br/>
The ''Display'' element is then textured with all the various pages' textures, called by the page-handler (''see'' here below).<br/>
Currently, I'm using the .jpg textures which I had previously generated through Photoshop; in the future they might be replaced by .svg files, depending from actual interactive use of some graphical objects (a few EFB pages do need interaction with graphical parts). Besides - if i'm not wrong - I've read somewhere on the FGWiki that gradients are not handled by the SVG parser...and I do like to use some gradients effects (antialiasing and such) to achieve a sort of realism on the displays.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213104#p213104
    |title=<nowiki>Re: 777 EFB: initial feedback</nowiki>
    |author=<nowiki>I-NEMO</nowiki>
    |date=<nowiki>Sat Jun 21</nowiki>
  }}
}}
{{FGCquote
  |that's the <u>current status</u> of the new 777 ''Seattle'''s EFB: it's still far from being perfect, but - as a newbie - I'm quite satisfied for the moment: I need to finish the first version fairly soon, because my to-do-list is long (I have to re-model all the aircraft fuselage [original model has wrong measures, ''sigh!''], produce better gears and flight-control surfaces model &amp; animations in Blender, and then to produce a new Paint-Kit in Photoshop; then all 3D models optimizations...and so forth; of course, we also have to take care of CDU, which will interface with the EFB. So, the job is still very, very long...
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213104#p213104
    |title=<nowiki>Re: 777 EFB: initial feedback</nowiki>
    |author=<nowiki>I-NEMO</nowiki>
    |date=<nowiki>Sat Jun 21</nowiki>
  }}
}}
{{FGCquote
  |The current EFB code is heavily focused on rendering raster images, which can be retained obviously, but in FG, we have additional means to render airport information that is 100% in sync with the FG side of things (navdb). <br/>
<br/>
For instance, we are going to "port" the airport-selection dialog to move rendering of airports/runways/taxiways/parking spots into dedicated MapStructure layers that can be properly styled and customized: [[Canvas_MapStructure#Porting_the_airports.xml_dialog]] <br/>
<br/>
[[File:Airport-selection-dialog.png|250px]]<br/>
<br/>
As you can probably tell, these kinds of layers would be very useful for any  kind of EFB related application.<br/>
<br/>
As long as the underlying design for a "page"-based MFD framework is sufficiently generic, we can easily replace/augment raster images and procedurally created charts - we could even use the built-in support for fetching via HTTP to download images on-line. In fact, we could then even extend Canvas to directly support rendering PDFs (OSG supports this out-of-the-box), this would make many steps unnecessary, because we could directly access [http://airnav.com http://airnav.com] without having to download/convert/ship any imagery. The code required to pull this off would be very compact in comparison.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213084#p213084
    |title=<nowiki>Re: 777 EFB: initial feedback</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Sat Jun 21</nowiki>
  }}
}}


Learn more at [[Canvas EFB Framework]] ...
Learn more at [[Canvas EFB Framework]] ...

Navigation menu