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:45, 22 October 2016
, 22 October 2016→Why Nasal and Canvas ?
(→FAQs) |
|||
| Line 165: | Line 165: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
there are different components available in FlightGear - as in an existing "Canvas GUI" SGSubsystem that runs inside the main loop, which all Canvas code can leverage - aside from that, there are widgets, and a framework to easily create new widgets - including a SVG parser that can reuse JavaScript/HTML based widgets. | |||
Apart from that, there is the pui2canvas parser that maps a subset of the legacy PUI markup to this existing infrastructure.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=289032#p289032 | |||
|title = <nowiki> Re: Aircraft Center | pui2canvas parser (devel-list follow-u </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Jun 18th, 2016 | |||
|added = Jun 18th, 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. | 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. | ||
| Line 176: | Line 188: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
== FAQs == | == FAQs == | ||