PUI: Difference between revisions

Jump to navigation Jump to search
40 bytes added ,  4 August 2020
m
→‎Replacement status: clean up / timeline
m (→‎Replacement status: https://sourceforge.net/p/flightgear/mailman/message/37077158/)
m (→‎Replacement status: clean up / timeline)
Line 18: Line 18:
{{See also|FlightGear_and_OpenGL_ES#Example:_disabling_PUI}}
{{See also|FlightGear_and_OpenGL_ES#Example:_disabling_PUI}}


=== 2020 ===
As of 03/2020, the PLIB replacement was reported to be in the backlog <ref>{{cite web
As of 03/2020, the PLIB replacement was reported to be in the backlog <ref>{{cite web
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/36951255/  
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/36951255/  
Line 38: Line 39:
In 08/2020, James stated that he was still working (exceptionally slowly!) on replacing PUI (as part of removing legacy OpenGL code (PUI, HUD, 2d panels, porting Canvas away form ShivaVG), so we can switch to Vulkan/VSG at some point (ideally at some point before Apple turn off OpenGL support…)), and that he doesn't think /any/ of us *want* to be working on these features particularly, but projects like these need to be done before anyone can have fun with VSG or Vulkan (personally James would be very enthusiastic about working on VSG support (being on macOS, I also have the most to lose / gain from it)). Sometimes that’s just how it goes. Equally they will all benefit the project ultimately, but the payoff both for the individual and the project is very drawn out. <ref>https://sourceforge.net/p/flightgear/mailman/message/37077158/</ref>
In 08/2020, James stated that he was still working (exceptionally slowly!) on replacing PUI (as part of removing legacy OpenGL code (PUI, HUD, 2d panels, porting Canvas away form ShivaVG), so we can switch to Vulkan/VSG at some point (ideally at some point before Apple turn off OpenGL support…)), and that he doesn't think /any/ of us *want* to be working on these features particularly, but projects like these need to be done before anyone can have fun with VSG or Vulkan (personally James would be very enthusiastic about working on VSG support (being on macOS, I also have the most to lose / gain from it)). Sometimes that’s just how it goes. Equally they will all benefit the project ultimately, but the payoff both for the individual and the project is very drawn out. <ref>https://sourceforge.net/p/flightgear/mailman/message/37077158/</ref>


=== 2019 ===
The new GUI has been incubating for a few years, but there's apparently been a lot of progress as of 10/2019.
The new GUI has been incubating for a few years, but there's apparently been a lot of progress as of 10/2019.


Line 45: Line 47:
   |title  =  <nowiki>Re: [Flightgear-devel] in Flightgear/Simgear C++ Code: What needs Doing? What are YOU Doing? What would you do if you had the time? </nowiki>  
   |title  =  <nowiki>Re: [Flightgear-devel] in Flightgear/Simgear C++ Code: What needs Doing? What are YOU Doing? What would you do if you had the time? </nowiki>  
   |author =  <nowiki> Scott Giese </nowiki>  
   |author =  <nowiki> Scott Giese </nowiki>  
   |date  =  Oct 14th, 2020
   |date  =  Oct 14th, 2019
   |added  =  Oct 14th, 2020
   |added  =  Oct 14th, 2019
   |script_version = 0.50  
   |script_version = 0.50  
   }}</ref>.
   }}</ref>.
Line 58: Line 60:
   |script_version = 0.40  
   |script_version = 0.40  
   }}</ref>
   }}</ref>
=== 2017 ===
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/  

Navigation menu