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 18:44, 22 October 2016
, 22 October 2016→FAQs
(→FAQs) |
|||
| Line 153: | Line 153: | ||
* PUI widget visibility controlled via props.nas (conditions) | * PUI widget visibility controlled via props.nas (conditions) | ||
* integration with the <code>canvas</code> tag to fully support recursion | * integration with the <code>canvas</code> tag to fully support recursion | ||
== Why Nasal and Canvas ? == | |||
Let's uppose we get super-fancy weather dialog. But the current weather dialog also works - because at the end of the day, what the dialogs do is set properties, execute FGCommands or start Nasal scripts. The fact that you have created a super-fancy dialog to do these tasks doesn't mean the simple one stops working. While the visuals of the dialogs can be really complicated, how the dialog communicates with FG is very well defined. | |||
It's like saying Phi will stop working because there's Qt - it won't, because internally it also sets properties, executes FGCommands or scripts. New widgets don't equal new ways to interact with FG for your module - how you interact with FG is determined by what the subsystems understand, not what your dialog does. | |||
The same way as a launcher is just a fancy way of assembling a commandline, and... you can just skip it and type the commandline.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=288966#p288966 | |||
|title = <nowiki> Re: Aircraft Center | pui2canvas parser (devel-list follow-u </nowiki> | |||
|author = <nowiki> Thorsten </nowiki> | |||
|date = Jun 17th, 2016 | |||
|added = Jun 17th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
Any UI talks to FG in terms of setting properties, calling FGcommands and Nasal scripts. Pretty much anyone who has done a glass cockpit for FG has solved the task. | |||
In fact, the Shuttle UI with the combination of MEDS/DPS pages, the keypad entry, the various keyboard to IDP to screen mappings and the major function/major mode constraints is ''much'' more complicated than FGs PUI. It'd be trivial (and amusing) to let some fictional Shuttle DPS pages control FG settings - it'd be straighforward to do because the DPS does what any GUI does - it communicates with FG via properties, FGCommands and scripts. | |||
So what some may call a 'mammoth' task (providing a graphical representation for communication with the rest of FG) is in fact exactly what canvas is for and what it does in every aircraft that uses a more advanced glass cockpit. Without any major problems really... Really all that is needed is the xml parser and the widgets - the rest is all there and has been used for years.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=289037#p289037 | |||
|title = <nowiki> Re: Aircraft Center | pui2canvas parser (devel-list follow-u </nowiki> | |||
|author = <nowiki> Thorsten </nowiki> | |||
|date = Jun 18th, 2016 | |||
|added = Jun 18th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
== FAQs == | == FAQs == | ||