20,741
edits
Canvas GUI: Difference between revisions
Jump to navigation
Jump to search
m
→PUI Widgets: http://flightgear.org/forums/viewtopic.php?f=71&t=17187&p=187244&hilit=canvas#p187245
m (→PUI Widgets: http://flightgear.org/forums/viewtopic.php?f=71&t=17187&p=187244&hilit=canvas#p187245) |
|||
| Line 30: | Line 30: | ||
== PUI Widgets == | == PUI Widgets == | ||
Implementing all our existing PUI/XML-based dialogs is almost certainly going to be more work than providing a Nasal-space migration path/wrapper that reads the old dialogs and turns them into "modern" canvas windows, possibly by just overwriting the dialog-show fgcommand via the new removecommand/addcommand APIs. And phasing out canvas widget should be fairly straightforward too, because those can be directly mapped to embedded/nested canvas textures, so I wouldn't worry too much ... | |||
All standard widgets (textbox, label, radio button, checkbox etc) can be provided by a Nasal parser that turns the existing GUI XML into canvas widgets - our hard-coded widgets however, need to be separately re-implemented. Here's a list of custom, hardcoded, PUI widgets which we will need to re-implement using the Canvas, based on [https://gitorious.org/fg/flightgear/trees/next/src/GUI $FG_SRC/GUI]: | All standard widgets (textbox, label, radio button, checkbox etc) can be provided by a Nasal parser that turns the existing GUI XML into canvas widgets - our hard-coded widgets however, need to be separately re-implemented. Here's a list of custom, hardcoded, PUI widgets which we will need to re-implement using the Canvas, based on [https://gitorious.org/fg/flightgear/trees/next/src/GUI $FG_SRC/GUI]: | ||