Howto:Using Driver Hashes in Nasal: Difference between revisions
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
== Objective == | == Objective == | ||
Demonstrate how to put context specific functionality (APIs) into so called '''driver hashes''' to easily switch between different front-ends or back-ends respectively. | Demonstrate how to put context specific functionality (APIs) into so called '''driver hashes''' to easily switch between different front-ends or back-ends respectively. | ||
== Problem == | |||
We have an increasing number of similar features that are sometimes even mutually incompatible, often this applies to features for which exist different alternatives/approaches, for example: | |||
* JSBSim vs. YASim | |||
* Basic Weather vs. Advanced Weather | |||
* Rembrandt vs. ALS | |||
* [[Phi]] vs. [[PUI]] | |||
== Background == | == Background == |
Revision as of 19:20, 14 October 2017
This article is a stub. You can help the wiki by expanding it. |
Objective
Demonstrate how to put context specific functionality (APIs) into so called driver hashes to easily switch between different front-ends or back-ends respectively.
Problem
We have an increasing number of similar features that are sometimes even mutually incompatible, often this applies to features for which exist different alternatives/approaches, for example:
Background
Related
References
|