Emesary MFD bridge: Difference between revisions
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
== Design Goals == | == Design Goals == | ||
[[File:ND-dialog-customizable-size-and-instances.png|thumb|Screenshot showing a [[PUI]] dialog with two [[NavDisplay]] instances, featuring support for customizable resolution/size of the ND as well as selectable number of NDs to be shown.]] | |||
{{See also|Howto:Prototyping a new NavDisplay Style}} | |||
The NavDisplay code is structured to support: | The NavDisplay code is structured to support: | ||
* GUI-based prototyping and design/testing of layers | |||
* truly indenpendent instances (an arbitrary number of them) | * truly indenpendent instances (an arbitrary number of them) | ||
* styling of ND layers/components according to aircraft specifics (think Boeing vs. Airbus ND) | * styling of ND layers/components according to aircraft specifics (think Boeing vs. Airbus ND) |
Revision as of 11:08, 14 October 2017
This article is a stub. You can help the wiki by expanding it. |
Objective
Document ongoing talks and ideas about using the Emesary framework to provide a sane interfacing mechanism for Canvas based avionics (and lower-level MapStructure building blocks]] using Richard's Canvas MFD Framework.
Background
Over time, the NavDisplay code has become a huge mess - it is far from being easily maintainable, yet it is the most widely used Canvas-based MFD in use today. So there are some lessons to be learnt from the whole experience.
Design Goals
See also Howto:Prototyping a new NavDisplay Style.
The NavDisplay code is structured to support:
- GUI-based prototyping and design/testing of layers
- truly indenpendent instances (an arbitrary number of them)
- styling of ND layers/components according to aircraft specifics (think Boeing vs. Airbus ND)
- encapsulate aircraft/system specifics (think differences between fdm, autopilot and route manager)
- encourage a modular and reusable design of additions, so that all aircraft developers using the framework can benefit automatically
Related
References
|