Work in progress This article or section will be worked on in the upcoming hours or days. See history for the latest developments. |
Objective
Illustrate the basic thought process required to come up with Nasal/Canvas code that is sufficiently generic to support the following requirements
- support multiple independent instances (e.g. PFDs or NDs)
- be aircraft/use-case agnostic (e.g. work without hard-coded properties)
- configurable without touching back-end code (e.g. via configuration hashes)
- modular (use separate files for splitting things up)
We'll be using the PFD/ND code as an example here, and won't be using any complicated techniques.