20,741
edits
m (→Replacement status: rewrite according to most recent statements) |
|||
Line 38: | Line 38: | ||
}}</ref>. | }}</ref>. | ||
In 02/2019, James stated that the new UI is coming quite soon. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/36589420/ | |||
|title = <nowiki> Re: [Flightgear-devel] Lagging </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = Feb 17th, 2019 | |||
|added = Feb 17th, 2019 | |||
|script_version = 0.40 | |||
}}</ref> | |||
In 10/2017, James said he was getting really close to having the PUI replacement UI suitable for beta-testing.<ref>{{cite web | In 10/2017, James said he was getting really close to having the PUI replacement UI suitable for beta-testing.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/36067646/ | |url = https://sourceforge.net/p/flightgear/mailman/message/36067646/ | ||
Line 48: | Line 56: | ||
}}</ref> | }}</ref> | ||
Originally, James was hoping to land the PUI replacement GUI in the last dev cycle in 2017 (at least as a proof-of-concept, probably not as the default UI), so wouldn’t expend lots of effort on things like collapsible sections which might be a lot of work with the current PUI/Canvas approaches, but are trivial with the new [[QtQuick use in FlightGear|QtQuick based UI scheme]].<ref>{{cite web | Originally, James was hoping to land the PUI replacement GUI in the last dev cycle in 2017 (at least as a proof-of-concept, probably not as the default UI), so wouldn’t expend lots of effort on things like collapsible sections which might be a lot of work with the current PUI/Canvas approaches, but are trivial with the new [[QtQuick use in FlightGear|QtQuick based UI scheme]].<ref>{{cite web |