20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
== Announcement == | == Announcement == | ||
There is currently (03/2015) heavy activity towards a new UI. There will be the HTML5/browser-based version (called [[Phi]]), TorstenD is currently working on, which will only be available after FlightGear has finished booting and initializing because it is a conventional FlightGear subsystem, as well as an internal implementation based on well supported libraries using Qt5 (which James Turner is working on), which will only be available during startup, and won't be running/available later on in its current form (i.e. at run-time), the latter having a strong focus on startup-relevant settings, while the former will only be able to deal with run-time settings. | There is currently (03/2015) heavy activity towards a new {{Abbr|UI|User Interface}}. There will be the HTML5/browser-based version (called [[Phi]]), TorstenD is currently working on, which will only be available after FlightGear has finished booting and initializing because it is a conventional FlightGear subsystem, as well as an internal implementation based on well supported libraries using Qt5 (which James Turner is working on), which will only be available during startup, and won't be running/available later on in its current form (i.e. at run-time), the latter having a strong focus on startup-relevant settings, while the former will only be able to deal with run-time settings. | ||
The parallel development of HTML and Qt based UI happens by intention and is not the result of missing coordination<ref>http://forum.flightgear.org/viewtopic.php?p=229445#p229445</ref>. Most likely, both will use a common service layer to provide necessary data<ref>http://forum.flightgear.org/viewtopic.php?p=229303#p229303</ref>. | The parallel development of HTML and Qt based UI happens by intention and is not the result of missing coordination<ref>http://forum.flightgear.org/viewtopic.php?p=229445#p229445</ref>. Most likely, both will use a common service layer to provide necessary data<ref>http://forum.flightgear.org/viewtopic.php?p=229303#p229303</ref>. | ||
James Turner is currently prototyping (at the suggestion/encouragement of Curt, Torsten D & others) a GUI integration for FlightGear based on Qt 5. This would overlap some areas other folks are working on, so we felt it best to make an announcement to avoid anyone expending their time on areas that might be affected<ref name="a">http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. | James Turner is currently prototyping (at the suggestion/encouragement of Curt, Torsten D & others) a {{Abbr|GUI|Graphical User Interface}} integration for FlightGear based on Qt 5. | ||
This would overlap some areas other folks are working on, so we felt it best to make an announcement to avoid anyone expending their time on areas that might be affected<ref name="a">http://sourceforge.net/p/flightgear/mailman/message/33245028/</ref>. | |||
All of this would be a QtQuick 2 GUI, not a Qt widgets GUI. If you don’t know what that terminology means, don’t worry about it, the quick answer is it works the same ways as Canvas does at present (rendering to OpenGL). | All of this would be a QtQuick 2 GUI, not a Qt widgets GUI. If you don’t know what that terminology means, don’t worry about it, the quick answer is it works the same ways as Canvas does at present (rendering to OpenGL). | ||