20,741
edits
Canvas widgets: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (→Nasal: remove obsolete stuff) |
No edit summary |
||
| Line 4: | Line 4: | ||
As of 07/2012, there's a general consensus to replace the current FlightGear GUI (based on PLIB/PUI) by using the new Canvas system. | As of 07/2012, there's a general consensus to replace the current FlightGear GUI (based on PLIB/PUI) by using the new Canvas system. | ||
{{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]]. | ||