FlightGear and OpenGL Core Profile: Difference between revisions

Jump to navigation Jump to search
m
→‎Affected features and sources: https://sourceforge.net/p/flightgear/mailman/message/37606344/
m (→‎Canvas.Path (OpenVG): https://forum.flightgear.org/viewtopic.php?f=71&t=39535&hilit=path+osg+canvas&start=60#p390834)
m (→‎Affected features and sources: https://sourceforge.net/p/flightgear/mailman/message/37606344/)
Line 233: Line 233:
|-
|-
! Feature !! Directory !! Notes !! Status  
! Feature !! Directory !! Notes !! Status  
|-
| [[HUD]] || $FG_SRC/HUD || One of the longterm development items we have is to replace the hardcoded HUD with one built on canvas.  As well as allowing us to remove anothe piece of plib, it would allow simple overlays like this as well.  So I think the answer here is to do that work, and then implement a canvas HUD for this overlay.<ref>https://sourceforge.net/p/flightgear/mailman/message/37606344/</ref>  || {{Progressbar|10}}
|-
|-
| [[PUI]] || $FG_SRC/GUI || trivial to disable, can be replaced via [[Phi]]. Is in the process of being replaced by an optional [[QtQuick use in FlightGear|QtQuick runtime]]  || {{Progressbar|70}}
| [[PUI]] || $FG_SRC/GUI || trivial to disable, can be replaced via [[Phi]]. Is in the process of being replaced by an optional [[QtQuick use in FlightGear|QtQuick runtime]]  || {{Progressbar|70}}

Navigation menu