20,741
edits
Canvas GUI: Difference between revisions
Jump to navigation
Jump to search
m
→PUI Widgets: http://gitorious.org/fg/flightgear/commit/38a373ba845d2bbea920cbcff90be5dc33040fe5
m (→Status 07/2013) |
m (→PUI Widgets: http://gitorious.org/fg/flightgear/commit/38a373ba845d2bbea920cbcff90be5dc33040fe5) |
||
| Line 32: | Line 32: | ||
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]: | ||
* [https://gitorious.org/fg/flightgear/blobs/next/src/GUI/MapWidget.cxx map widget] see [[Canvas Map API]]) <font color="red">porting should probably be prioritized, because we keep seeing additions to the PUI/C++ widget despite the canvas:</font> | |||
** [http://gitorious.org/fg/flightgear/commit/433af2b51a3bcec7488ac2fbf94b8edfc1e1cb43 Flight-path-history.] | |||
** [http://gitorious.org/fg/flightgear/commit/11c00afaec8836a5f52bcf8832ff2d50e2f11523 Add support for helipads from apt.dat 850+] | |||
** [http://gitorious.org/fg/flightgear/commit/6bf47cd248ed388e6a4dd3ffa2d00977b00b62fb MapWidget: make use of the new POI system and display cities on the map. This is meant as a preview.] | |||
** [http://gitorious.org/fg/flightgear/commit/658bda6e40da65c317fd387ed1a2fcf628e7ed1b MapWidget: Show counties and towns as well, depending on the zoom. Some colors added.] | |||
** [http://gitorious.org/fg/flightgear/commit/38a373ba845d2bbea920cbcff90be5dc33040fe5 Display AI traffic route in map. Add some helpers so MapWidget can show the origin and destination of AIAircraft with a FlightPlan.] | |||
* [https://gitorious.org/fg/flightgear/blobs/next/src/GUI/FGPUIDialog.cxx#line169 loglist] {{progressbar|70}} | * [https://gitorious.org/fg/flightgear/blobs/next/src/GUI/FGPUIDialog.cxx#line169 loglist] {{progressbar|70}} | ||
** Required APIs: logbuffer needs to be exposed to Nasal via cppbind | ** Required APIs: logbuffer needs to be exposed to Nasal via cppbind | ||
| Line 41: | Line 47: | ||
* [https://gitorious.org/fg/flightgear/blobs/next/src/GUI/PUIFileDialog.cxx file dialog] | * [https://gitorious.org/fg/flightgear/blobs/next/src/GUI/PUIFileDialog.cxx file dialog] | ||
* [https://gitorious.org/fg/flightgear/blobs/next/src/GUI/menubar.cxx menubar] | * [https://gitorious.org/fg/flightgear/blobs/next/src/GUI/menubar.cxx menubar] | ||
In order to re-implement these using the Canvas system, we need to identify Nasal APIs that are currently missing, and which need to be provided via the cppbind framework. | In order to re-implement these using the Canvas system, we need to identify Nasal APIs that are currently missing, and which need to be provided via the cppbind framework. | ||