20,741
edits
m (→Objective: http://forum.flightgear.org/viewtopic.php?f=71&t=23650&p=215310#p215310) |
|||
Line 3: | Line 3: | ||
== Objective == | == Objective == | ||
Illustrate the basic thought process required to come up with Nasal/Canvas code that is sufficiently generic to meet the following requirements | Illustrate the basic thought process required to come up with Nasal/Canvas code that is sufficiently generic to meet the following requirements | ||
* support multiple independent instances (e.g. PFDs | * support multiple independent instances (e.g. PFDs, NDs, EFBs, CDUs) | ||
* be aircraft/use-case agnostic (e.g. work without hard-coded properties) | * be aircraft/use-case agnostic (e.g. work without hard-coded properties) | ||
* make aircraft-specific settings configurable, e.g. number of engines, by [[Howto:Start using vectors and hashes in Nasal|using vectors and hashes]] | * make aircraft-specific settings configurable, e.g. number of engines, by [[Howto:Start using vectors and hashes in Nasal|using vectors and hashes]] | ||
* configurable without touching back-end code (e.g. via configuration hashes) | * configurable without touching back-end code (e.g. via configuration hashes) | ||
* support stying and custom properties via configuration hashes | |||
* modular (use separate files for splitting things up) | * modular (use separate files for splitting things up) | ||