Canvas EFB framework: Difference between revisions

Jump to navigation Jump to search
m
Line 266: Line 266:
}}
}}


=== 777 EFB Roadmap ===
== 777 EFB Roadmap ==
=== Page Handling ===
{{cquote
{{cquote
   |<nowiki>Page Handling Parser: what would be your advice? Could you give me some working examples - consistent with my actual EFB framework - to be tested inside my code?</nowiki><br/><nowiki>
   |<nowiki>Page Handling Parser: what would be your advice? Could you give me some working examples - consistent with my actual EFB framework - to be tested inside my code?</nowiki><br/><nowiki>
Line 294: Line 295:
   }}
   }}
}}
}}
{{cquote
  |<nowiki> I really suggest to take a quick look at F-JJTH GPSMap196 - it's still a stub, much less functional than your work, but at least the code is compact that way. Understanding classes/OOP would be helpful though, but that will greatly simplify all your other work either way. So it would be worthwhile to read up a bit on OO and maybe work through 2-3 tutorials, or even just play with classes in the Nasal console. Let me know if you have any questions - better use the wiki for OO question, so that we can directly update the corresponding articles.</nowiki>
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211557#p211557
    |title=<nowiki>Re: 777 EFB status & plans  ?</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Tue Jun 03</nowiki>
  }}
}}
=== Text Handling ===


{{cquote
{{cquote
Line 307: Line 319:


{{cquote
{{cquote
   |<nowiki>Procedural Charts: I don't like the idea at the moment: I've seen some tests you proposed in the developmnet of the 'Airport Location' dialog: looking at Boeing manuals we want to stick to real charts, hi-res, full of details for the pilot; we just want to display a crisp nice .jpg, or .png, or svg, file on the screen (Boeing 777's EFB has a fixed ratio of 1.412371 proportion between width and height); a nice possibility, though, would be to superimpose some symbols over those charts, in time)</nowiki>
   |<nowiki>Regarding your current way of text handling, yes, there is a much better way using Canvas - you are still using the old method that people used to use when canvas was not around, it is now deprecated. Like you say, the whole XML/setprop mess can be avoided these days by using Canvas. TheTom's CDU framework is using the new method</nowiki>
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211557#p211557
    |title=<nowiki>Re: 777 EFB status & plans  ?</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Tue Jun 03</nowiki>
  }}
}}
 
=== Procedural Charts ===
{{cquote
  |<nowiki>I don't like the idea at the moment: I've seen some tests you proposed in the developmnet of the 'Airport Location' dialog: looking at Boeing manuals we want to stick to real charts, hi-res, full of details for the pilot; we just want to display a crisp nice .jpg, or .png, or svg, file on the screen (Boeing 777's EFB has a fixed ratio of 1.412371 proportion between width and height); a nice possibility, though, would be to superimpose some symbols over those charts, in time)</nowiki>
   |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211554#p211554
   |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211554#p211554
     |title=<nowiki>Re: 777 EFB status & plans  ?</nowiki>
     |title=<nowiki>Re: 777 EFB status & plans  ?</nowiki>
     |author=<nowiki>I-NEMO</nowiki>
     |author=<nowiki>I-NEMO</nowiki>
    |date=<nowiki>Tue Jun 03</nowiki>
  }}
}}
{{cquote
  |<nowiki>Procedural charts are not needed - PDFs converted to PNGs should work just fine. Displaying symbol overlays is straightforward to do using Canvas, and those could even be moving and animated symbols using the MapStructure framework</nowiki>
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211557#p211557
    |title=<nowiki>Re: 777 EFB status & plans  ?</nowiki>
    |author=<nowiki>Hooray</nowiki>
     |date=<nowiki>Tue Jun 03</nowiki>
     |date=<nowiki>Tue Jun 03</nowiki>
   }}
   }}

Navigation menu