20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
m
→Canvas: http://sourceforge.net/p/flightgear/mailman/message/34196458/
m (→Dependencies) |
m (→Canvas: http://sourceforge.net/p/flightgear/mailman/message/34196458/) |
||
| Line 70: | Line 70: | ||
=== Canvas === | === Canvas === | ||
{{Note|Building a QT based GUI is not in any way meant to obstruct the further development of a Canvas based GUI. We did voice some concerns as to whether the need to re-implement a complete | |||
widget is worth the cost is terms of development effort. The beauty of open source is that there's more than one way to do things, however. Especially in a completely modular environment (via [[HLA]]) [http://sourceforge.net/p/flightgear/mailman/message/34196458/]. | |||
}} | |||
James isn't expecting many issues integrating Canvas layers with a Qt GUI, so there is no wasted development effort there (There is the possibility to make a [[Canvas]] backend based upon QPainter, which might be a great way to use spare CPU cycles to unload the GPU, however, as Canvas rendering becomes more intensive)<ref name="a">http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. However, at least for the time being, the Qt5 GUI is not even available at run-time, but will be shut down after handing over control to the main FlightGear initialization routines. | James isn't expecting many issues integrating Canvas layers with a Qt GUI, so there is no wasted development effort there (There is the possibility to make a [[Canvas]] backend based upon QPainter, which might be a great way to use spare CPU cycles to unload the GPU, however, as Canvas rendering becomes more intensive)<ref name="a">http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. However, at least for the time being, the Qt5 GUI is not even available at run-time, but will be shut down after handing over control to the main FlightGear initialization routines. | ||