20,741
edits
UI Unification: Difference between revisions
Jump to navigation
Jump to search
→Motivation
| Line 12: | Line 12: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
Of course, it should be possible to support the current XML syntax using any toolkit, it just's a question of how hard it is.<ref>{{cite web | Of course, it should be possible to support the current XML syntax using any toolkit, it just's a question of how hard it is.<ref>{{cite web | ||
| Line 20: | Line 19: | ||
|date = Jul 24th, 2012 | |date = Jul 24th, 2012 | ||
|added = Jul 24th, 2012 | |added = Jul 24th, 2012 | ||
|script_version = 0.40 | |||
}}</ref> | |||
Regarding the Canvas GUI system, we could for example just add some more parseXXX functions (like parsesvg) which parse a dialog/hud/whathever file and create a canvas from it. So we would just have to modify eg. the {{fgcommand|show-dialog}} command to create a canvas and call the parser.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/29589689/ | |||
|title = <nowiki> Re: [Flightgear-devel] Switching from PUI to osgWidget </nowiki> | |||
|author = <nowiki> Thomas Geymayer </nowiki> | |||
|date = Jul 25th, 2012 | |||
|added = Jul 25th, 2012 | |||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||