20,741
edits
Canvas widgets: Difference between revisions
Jump to navigation
Jump to search
m
provide some context & pointers for people looking for related info, as per: https://code.google.com/p/flightgear-bugs/issues/detail?id=1295#c2
No edit summary |
m (provide some context & pointers for people looking for related info, as per: https://code.google.com/p/flightgear-bugs/issues/detail?id=1295#c2) |
||
| Line 12: | Line 12: | ||
}} | }} | ||
}} | }} | ||
{{FGCquote | |||
|The "built-in" GUI/launcher is one of the longest-standing feature requests - but it's not just about the GUI (which is rather straightforward in comparison), but about the simulator never having been developed with this requirement, i.e. run-time reinitialization, in mind - thus, things like "fgrun" (and a plethora of other external launchers) were developed, which acted as a front-end on top of FG, so that FG itself wouldn't need to be changed - i.e. kind of a "remote control" using command line arguments. So it's there for a reason - fgrun uses the FLTK GUI library, which while relatively simple, is much more powerful than our legacy GUI engine, PUI. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213461#p213461 | |||
|title=<nowiki>Re: About FlightGear being user-friendly or not</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Thu Jun 26</nowiki> | |||
}} | |||
}} | |||
However, before we can work on adding new widgets to FlightGear, we need to provide wrappers for the existing hardcoded PUI widgets, see [[Canvas GUI]]. | However, before we can work on adding new widgets to FlightGear, we need to provide wrappers for the existing hardcoded PUI widgets, see [[Canvas GUI]]. | ||