20,741
edits
Canvas widgets: Difference between revisions
Jump to navigation
Jump to search
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) |
No edit summary |
||
| Line 5: | Line 5: | ||
{{FGCquote | {{FGCquote | ||
|The | |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= | |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213461#p213461 | ||
|title=<nowiki>Re: About FlightGear being user-friendly or not</nowiki> | |title=<nowiki>Re: About FlightGear being user-friendly or not</nowiki> | ||
|author=<nowiki> | |author=<nowiki>Hooray</nowiki> | ||
|date=<nowiki> | |date=<nowiki>Thu Jun 26</nowiki> | ||
}} | }} | ||
}} | }} | ||
{{FGCquote | {{FGCquote | ||
| | |This is something that is currently being addressed by TheTom and Zakalawe, who've both been working on a new Canvas GUI, and a new Canvas GUI dialog called "Aircraft Center", which -while still experimental- is intended to eventually allow end-users to easily download/install aircraft right within the simulator, and also switch between aircraft at run-time without having to exit/restart the simulator.<br/> | ||
<br/> | |||
Thus, adopting Canvas is going to address a number of long-standing issues, but it's obviously a process that only just got started, and it will not happen overnight - 2-3 release cycles are not far-fetched, that's how long the whole migration could very well take, unless there are more people interested in helping. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213461#p213461 | |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213461#p213461 | ||
|title=<nowiki>Re: About FlightGear being user-friendly or not</nowiki> | |title=<nowiki>Re: About FlightGear being user-friendly or not</nowiki> | ||
| Line 21: | Line 23: | ||
}} | }} | ||
{{FGCquote | |||
|The [[Aircraft Center]] has started on that (providing a built-in GUI), and Tom's recent work has made it many times more feasible to imagine more complex dialogs as well as James' work on the C++ side. Canvas technically has the capability to do most GUI functions, it just requires a "little" work to be put in to get it there ;). I think we have at least 4 people involved already in seriously using Canvas in the GUI, so there's a high probability that it'll be adopted quite fast (I've already realized two pretty cool dialogs with it | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213608#p213608 | |||
|title=<nowiki>Re: About FlightGear being user-friendly or not</nowiki> | |||
|author=<nowiki>Philosopher</nowiki> | |||
|date=<nowiki>Fri Jun 27</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]]. | ||