PUI: Difference between revisions

Jump to navigation Jump to search
500 bytes added ,  25 January 2017
no edit summary
No edit summary
No edit summary
Line 29: Line 29:


PUI is also known to affect rendering performance quite significantly, while also preventing FlightGear from using a more recent version of OpenGL<ref>http://sourceforge.net/p/flightgear/mailman/message/34532040/</ref><ref>http://forum.flightgear.org/viewtopic.php?f=71&t=24046</ref>.  
PUI is also known to affect rendering performance quite significantly, while also preventing FlightGear from using a more recent version of OpenGL<ref>http://sourceforge.net/p/flightgear/mailman/message/34532040/</ref><ref>http://forum.flightgear.org/viewtopic.php?f=71&t=24046</ref>.  
However, improving the frame-rate and modernised 3D rendering,  can’t be worked on until the PUI code, 2D panels and Shiva are removed, but doing so is a frustrating slow path<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35623408/
  |title  =  <nowiki> Re: [Flightgear-devel] canvas non svg-elements broken </nowiki>
  |author =  <nowiki> James Turner </nowiki>
  |date  =  Jan 24th, 2017
  |added  =  Jan 24th, 2017
  |script_version = 0.40
  }}</ref>


In addition, [[OpenSceneGraph]] (OSG) can obviously not help optimize any PUI related GL code and PUI widgets are generally considered to be pretty archaic and not easy to extend<ref>http://sourceforge.net/p/flightgear/mailman/message/26832164/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/10587120/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/10587272/</ref>.
In addition, [[OpenSceneGraph]] (OSG) can obviously not help optimize any PUI related GL code and PUI widgets are generally considered to be pretty archaic and not easy to extend<ref>http://sourceforge.net/p/flightgear/mailman/message/26832164/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/10587120/</ref><ref>http://sourceforge.net/p/flightgear/mailman/message/10587272/</ref>.

Navigation menu