20,741
edits
Canvas EFB framework: Difference between revisions
Jump to navigation
Jump to search
m
→Design
m (the 777 now contains a prototype) |
m (→Design) |
||
| Line 141: | Line 141: | ||
[[File:777-EFB-MAIN.png|thumb|777-200ER EFB [http://forum.flightgear.org/viewtopic.php?f=71&t=23196]]] | [[File:777-EFB-MAIN.png|thumb|777-200ER EFB [http://forum.flightgear.org/viewtopic.php?f=71&t=23196]]] | ||
[[File:777-EFB-AIRPORT-SEARCH.png|thumb|777-200 EFB AIRPORT SEARCH, see [http://forum.flightgear.org/viewtopic.php?f=71&t=23196&p=211410#p211410]]] | [[File:777-EFB-AIRPORT-SEARCH.png|thumb|777-200 EFB AIRPORT SEARCH, see [http://forum.flightgear.org/viewtopic.php?f=71&t=23196&p=211410#p211410]]] | ||
== The 777 EFB == | |||
{{cquote | |||
|<nowiki> like the fact that the code is using hashes to configure some things at the top of the file, but otherwise, it's still fairly non-generic and not very flexible at the moment. And structurally it is certainly overlapping with existing code, such as the Avidyne Entegra, or even just the GPSMap196 - especially the page handling and mode switching stuff is not yet sufficiently generic. There's a reason that we've been discussing a generic Canvas-based EFB framework, which should ideally use a common "MFD" framework</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211410#p211410 | |||
|title=<nowiki>777 EFB status & plans ?</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sun Jun 01</nowiki> | |||
}} | |||
}} | |||
{{cquote | |||
|<nowiki>Functionality-wise there seem to be a lot of corner cases handled already by the efb.nas file:</nowiki> https://gitorious.org/fg/fgdata/source/Aircraft/777/Nasal/efb.nas<nowiki> | |||
But especially event handling and mode switching is extremely explicit and non-generic at the moment, a problem that the original GPSMap196 code also had - the whole thing could probably be reduced by about 60% if we could work out a way to find common goals | |||
And the whole point is flexibility and generic code, so that things like the ND, PFD or EFB use the same back-end for implementing MFDs, and the same back-end for event handling, including page- and mode management.</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211410#p211410 | |||
|title=<nowiki>777 EFB status & plans ?</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sun Jun 01</nowiki> | |||
}} | |||
}} | |||
{{cquote | |||
|<nowiki>The basic recipe to make this sufficiently generic is basically what we did with Gijs' original ND code: | |||
</nowiki> | |||
* supporting multiple independent instances/instruments | |||
* supporting different aircraft | |||
* extracting useful code and generalizing it | |||
* integrating the whole thing with existing instruments (ND, PFD, EICAS) | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211410#p211410 | |||
|title=<nowiki>777 EFB status & plans ?</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sun Jun 01</nowiki> | |||
}} | |||
}} | |||
== Design == | == Design == | ||