20,741
edits
Canvas EFB framework: Difference between revisions
Jump to navigation
Jump to search
→The 777 EFB
No edit summary |
|||
| Line 263: | Line 263: | ||
|author=<nowiki>Hooray</nowiki> | |author=<nowiki>Hooray</nowiki> | ||
|date=<nowiki>Sun Jun 01</nowiki> | |date=<nowiki>Sun Jun 01</nowiki> | ||
}} | |||
}} | |||
=== 777 EFB Roadmap === | |||
{{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> | |||
I would test them, study them and come back with deeper questions and so forth.</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211554#p211554 | |||
|title=<nowiki>Re: 777 EFB status & plans ?</nowiki> | |||
|author=<nowiki>I-NEMO</nowiki> | |||
|date=<nowiki>Tue Jun 03</nowiki> | |||
}} | |||
}} | |||
{{cquote | |||
|<nowiki>I'd like to get a crystal-clear example about integrating a Canvas screen for a given page (remember I'm an old-school man, I like to be detailed; even if a concept is new to me, I first want to proper understand the Philosophy behind a certain solution, then I would study the logic, and then the syntax): how to create the instance, how to define properties like size, content, interactions and so forth.</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211554#p211554 | |||
|title=<nowiki>Re: 777 EFB status & plans ?</nowiki> | |||
|author=<nowiki>I-NEMO</nowiki> | |||
|date=<nowiki>Tue Jun 03</nowiki> | |||
}} | |||
}} | |||
{{cquote | |||
|<nowiki>I presume I could elaborate and reproduce it all along my current code, and get back to you with problems and results, so to solve issues, refine the coding, and to get it work...</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211554#p211554 | |||
|title=<nowiki>Re: 777 EFB status & plans ?</nowiki> | |||
|author=<nowiki>I-NEMO</nowiki> | |||
|date=<nowiki>Tue Jun 03</nowiki> | |||
}} | |||
}} | |||
{{cquote | |||
|<nowiki>the Text object matrix is made by about 20 lines of text (to be consistent with some added applications, like the Descent Rate calculator, I had to add some more lines with different horizontal, vertical position on the screen, and different Font Size).</nowiki><br/><nowiki> | |||
The piece of .xml code (EFB_display_lines.xml) which handles a given line of text (taken from Omega95' software) is quite large; so, I splitted the .xml related to all the text lines from the main EFB xml.</nowiki><br/><nowiki> | |||
Still, I do not like it at all: is there a better solution for that?...the ideal would be to have just one piece of code to display a line, and a bunch of, say, 15 variables for all the various text properties (positions, alignment, font, font size, character size, and so forth); can nasal pass these variables to .xml withour addressing each time a setprop call? Or, even better: can we avoid .xml coding for the text matrix, and handle it from within nasal?</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211554#p211554 | |||
|title=<nowiki>Re: 777 EFB status & plans ?</nowiki> | |||
|author=<nowiki>I-NEMO</nowiki> | |||
|date=<nowiki>Tue Jun 03</nowiki> | |||
}} | |||
}} | |||
{{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> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211554#p211554 | |||
|title=<nowiki>Re: 777 EFB status & plans ?</nowiki> | |||
|author=<nowiki>I-NEMO</nowiki> | |||
|date=<nowiki>Tue Jun 03</nowiki> | |||
}} | }} | ||
}} | }} | ||