252
edits
Modules.nas: Difference between revisions
Jump to navigation
Jump to search
→HowTo / Examples
| (2 intermediate revisions by the same user not shown) | |||
| Line 82: | Line 82: | ||
You can also call {{code| myAircraft.my_efis.reload();}} to trigger the reload. myAircraft is the namespace given in the <aircraft>-set.xml file, my_efis is the module object (see above). | You can also call {{code| myAircraft.my_efis.reload();}} to trigger the reload. myAircraft is the namespace given in the <aircraft>-set.xml file, my_efis is the module object (see above). | ||
|margin=10px |width=50%}} | |margin=10px |width=50%}} | ||
== Nasal frameworks == | |||
Another usecase for Modules.nas is frameworks that need reload support. | |||
A framework usually provides more or less generic functionality that has to be adapted (configured) for a specific usecase (e.g. a specific aircraft). | |||
Reload support may become very convenient, if the customizing based on such framework involves many iterations of edit-reload-test. | |||
= Structure of Nasal reloadable modules = | = Structure of Nasal reloadable modules = | ||
| Line 221: | Line 226: | ||
}} | }} | ||
= Existing modules = | = Existing modules with reload support = | ||
Stable Nasal frameworks which support reloading can be added to ''FGDATA/Nasal/modules/<module_name>''. | |||
This allows an aircraft developer to configure the framework for a specific aircraft and make use of the reload magic while developing the configuration. | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! Module name !! Desctiption !! time added | ! Module name !! Desctiption !! time added | ||
|- | |- | ||
| canvas_efis || framework to manage canvas based EFIS screens || | | [[Canvas EFIS Framework|canvas_efis]] || framework to manage canvas based EFIS screens || 02/2020 | ||
|} | |} | ||