6,566
edits
Canvas EFB framework: Difference between revisions
Jump to navigation
Jump to search
Switch to {{flightgear url}}, {{simgear url}}, {{gitorious url}}, {{fgaddon file}}, and {{gitorious source}} to fix the broken Gitorious links.
m (→Canvas & PDF: https://searchcode.com/codesearch/view/20919788/) |
(Switch to {{flightgear url}}, {{simgear url}}, {{gitorious url}}, {{fgaddon file}}, and {{gitorious source}} to fix the broken Gitorious links.) |
||
| Line 15: | Line 15: | ||
|maintainers = | |maintainers = | ||
|developers = I-NEMO, Hyde, Hooray | |developers = I-NEMO, Hyde, Hooray | ||
|folders = {{flightgear url|src/Canvas|pre=$FG_SRC}} | |||
|folders = | {{simgear url|simgear/canvas|pre=$SG_SRC}} | ||
|topic-fgdata= (main repository, master branch; {{gitorious url|proj=fg|repo=toms-fgdata|branch=canvas-gui-demo|view=shortlog}}) | |||
|topic-fgdata= (main repository, master branch; | |||
|subforum= http://forum.flightgear.org/viewforum.php?f=71 | |subforum= http://forum.flightgear.org/viewforum.php?f=71 | ||
}} | }} | ||
| Line 291: | Line 289: | ||
{{cquote | {{cquote | ||
|<nowiki>Functionality-wise there seem to be a lot of corner cases handled already by the efb.nas file:</nowiki> | |<nowiki>Functionality-wise there seem to be a lot of corner cases handled already by the efb.nas file:</nowiki> {{fgaddon file|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 | 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 | ||
| Line 407: | Line 405: | ||
Regarding init/start/update/stop methods, those would be straightforward to have/add, currently the code is just structured such that this is all handled by the page manager. I kind of introduced that assumption a while ago to get rid of all the explicit polling and settimer/maketimer weirdness, because there was some discussion about having one timer/callback per "page", which was a bit concerning :D <br/> | Regarding init/start/update/stop methods, those would be straightforward to have/add, currently the code is just structured such that this is all handled by the page manager. I kind of introduced that assumption a while ago to get rid of all the explicit polling and settimer/maketimer weirdness, because there was some discussion about having one timer/callback per "page", which was a bit concerning :D <br/> | ||
<br/> | <br/> | ||
{{gitorious source|proj=fg|repo=canvas-hackers-fgdata|commit=b6f4c80e2ac439db6f72c291a66ca3010f91e21d|path=Aircraft/Instruments-3d/GPSmap196/mfd.nas}}<br/> | |||
<br/> | <br/> | ||
Technically, I was really just using those experiments to come up with something more flexible in XML space (where we could trivially support such code blocks/tags), which I am hoping to extend over time, assuming that people would be willing to adopt such a system: [http://forum.flightgear.org/viewtopic.php?p{{=}}212029#p212029 Subject: Framework-centric aircraft-agnostic avionics development] | Technically, I was really just using those experiments to come up with something more flexible in XML space (where we could trivially support such code blocks/tags), which I am hoping to extend over time, assuming that people would be willing to adopt such a system: [http://forum.flightgear.org/viewtopic.php?p{{=}}212029#p212029 Subject: Framework-centric aircraft-agnostic avionics development] | ||