20,741
edits
Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions
Jump to navigation
Jump to search
Howto:Processing legacy PUI dialogs using Canvas (view source)
Revision as of 19:11, 21 June 2016
, 21 June 2016→Approach
| Line 831: | Line 831: | ||
For prototyping purposes, we will be registering [[Howto:Add new fgcommands to FlightGear#Background|a custom fgcommand]] in [[Nasal]] using the {{func link|addcommand()}} API and patch [[Menubar|menubar.xml]] to change <code>dialog-show</code> fgcommands (as per {{readme file|commands}}) into <code>canvas-dialog-show</code> for each dialog whose widgets are supported/ported. | For prototyping purposes, we will be registering [[Howto:Add new fgcommands to FlightGear#Background|a custom fgcommand]] in [[Nasal]] using the {{func link|addcommand()}} API and patch [[Menubar|menubar.xml]] to change <code>dialog-show</code> fgcommands (as per {{readme file|commands}}) into <code>canvas-dialog-show</code> for each dialog whose widgets are supported/ported. | ||
For starters, we will focus on simple dialogs, such as exit | For starters, we will focus on simple dialogs, such as {{GUI dialog|dialog=about}} and {{GUI dialog|dialog=exit}} — however, the framework will be sufficiently generic to also support other widgets/dialogs (as per README.gui). | ||
Once a sufficiently-large subset of PUI widgets are supported by the parser, it would also be possible to override the {{fgcommand|dialog-show}} command directly to circumvent the underlying PUI C++ code, which could then also be disabled, phased out/removed in its entirety. | Once a sufficiently-large subset of PUI widgets are supported by the parser, it would also be possible to override the {{fgcommand|dialog-show}} command directly to circumvent the underlying PUI C++ code, which could then also be disabled, phased out/removed in its entirety. | ||