20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
m (de-quoting) |
mNo edit summary |
||
| Line 14: | Line 14: | ||
Expect to see a test branch in Git in the next month or so, and hopefully something usable for 3.6. Note that even in this (slightly optimistic) case, there will be some limitations, e.g. multi-window setup will not work in Qt builds without further work. The PLIB code will remain so hopefully it can be a gradual transition<ref>http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. | Expect to see a test branch in Git in the next month or so, and hopefully something usable for 3.6. Note that even in this (slightly optimistic) case, there will be some limitations, e.g. multi-window setup will not work in Qt builds without further work. The PLIB code will remain so hopefully it can be a gradual transition<ref>http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. | ||
Some code James has written in the 2014 will be obsolete, e.g. the native message box and menubar code. 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>http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. | Some code James has written in the 2014 will be obsolete, e.g. the native message box and menubar code. 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>http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. | ||
== Background == | == Background == | ||