20,741
edits
Initializing Nasal early: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 50: | Line 50: | ||
{{FGCquote|1= This is exactly what I added support for implementing new commands in Nasal, so that going forward we can correctly put custom dynamic things in commands. |2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=191781#p191781 | title = <nowiki>Re: Modular Nasal bootstrapping (again)</nowiki> | author = <nowiki>zakalawe</nowiki> | date = Oct 14th, 2013 }}}} | {{FGCquote|1= This is exactly what I added support for implementing new commands in Nasal, so that going forward we can correctly put custom dynamic things in commands. |2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=191781#p191781 | title = <nowiki>Re: Modular Nasal bootstrapping (again)</nowiki> | author = <nowiki>zakalawe</nowiki> | date = Oct 14th, 2013 }}}} | ||
{{FGCquote | |||
|1= on the complexity of dependencies for Nasal scripts, I think again the answer is to have the running status of each subsystem stored somewhere, and exposed via the property tree. The trick will be picking good groups, so most things have one or two dependencies, and having some documentation somewhere stating what's in each group. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/13175741/ | |||
| title = <nowiki>Re: [Flightgear-devel] Subsystem run-levels</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Apr 18th, 2006 | |||
| added = Apr 18th, 2006 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||