20,741
edits
Line 273: | Line 273: | ||
}} | }} | ||
</ref> | </ref> | ||
it would be a good idea to localie any custom Nasal blocks, and instead introduce custom fgcommands using the addcommand() API - basically the reason being that there could be an aircraft-specific API using fgcommands for starting engines, instead of having aircraft-specific "Nasal blobs" in each checklist file. A while ago, this was actually discussed on the devel list, too. In other words, an "fgcommand" (implemented in Nasal) would help better isolate checklists from aircraft specifics. | |||
<ref> {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=241259#p241259 | |||
| title = <nowiki>Re: Automated Checklist Execution</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = May 1st, 2015 | |||
| added = May 1st, 2015 | |||
| script_version = 0.25 | |||
}} | |||
</ref> | |||
== External link == | == External link == | ||
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38325.html Aircraft Checklists] (mailing list) | * [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38325.html Aircraft Checklists] (mailing list) |