Changes

Jump to navigation Jump to search
Line 234: Line 234:  
! Feature !! Directory !! Notes !! Status  
 
! Feature !! Directory !! Notes !! Status  
 
|-
 
|-
| [[PUI]] || $FG_SRC/GUI || trivial to disable, can be replaced via [[Phi]] || {{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}}
 
|-
 
|-
| [[FGPanel|2D Panels]] || $FG_SRC/Cockpit || legacy 2D panels (could use [[Canvas]]), actually as of 04/2020, there is now a dedicated OpenGL ES based version of the standalone fgpanel port available which could be backported (mainly contains hard-coded shader updates) <ref>https://sourceforge.net/p/flightgear/flightgear/ci/dc6fb535962eff8214bc5b1708886178cceb482e/log/?path=/utils/fgpanel</ref> See also merge request {{Merge-request|project=flightgear|id=191|text=#191:HLA update + fgpanel on Raspberry Pi}} and the discussion <ref>https://sourceforge.net/p/flightgear/mailman/message/36978512/</ref>
+
| [[Post_FlightGear_2020.2_LTS_changes#2D_Panels|2D Panels]] || $FG_SRC/Cockpit || legacy 2D panels (could use [[Canvas]]), actually as of 04/2020, there is now a dedicated OpenGL ES based version of the standalone fgpanel port available which could be backported (mainly contains hard-coded shader updates) <ref>https://sourceforge.net/p/flightgear/flightgear/ci/dc6fb535962eff8214bc5b1708886178cceb482e/log/?path=/utils/fgpanel</ref> See also merge request {{Merge-request|project=flightgear|id=191|text=#191:HLA update + fgpanel on Raspberry Pi}} and the discussion <ref>https://sourceforge.net/p/flightgear/mailman/message/36978512/</ref>
    
There's also a [https://sourceforge.net/p/flightgear/flightgear/ci/topics/panel-hacking/~/tree/ branch] (which is a few of years old) contains WIP on implementing 2D panels as canvas. It uses the same loading / updating logic in C++ (for 100% compatibility), but rather than building custom rendering, it builds up a Canvas element hierarchy in C++.<ref>https://sourceforge.net/p/flightgear/mailman/message/36980724/</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/37042351/</ref>
 
There's also a [https://sourceforge.net/p/flightgear/flightgear/ci/topics/panel-hacking/~/tree/ branch] (which is a few of years old) contains WIP on implementing 2D panels as canvas. It uses the same loading / updating logic in C++ (for 100% compatibility), but rather than building custom rendering, it builds up a Canvas element hierarchy in C++.<ref>https://sourceforge.net/p/flightgear/mailman/message/36980724/</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/37042351/</ref>
|| {{Pending}}
+
|| {{Progressbar|80}}
 
|-
 
|-
| [[Canvas Path]] (Shiva) || $SG_SRC/canvas || needs some thinking, probably native OpenVG on RPi <ref>https://github.com/ajstarks/openvg</ref> <ref>http://mindchunk.blogspot.com/2012/09/openvg-on-raspberry-pi.html</ref> or an OpenGL based implementation like nanovg <ref>https://www.raspberrypi.org/forums/viewtopic.php?t=247586#p1516785</ref> || {{Pending}}
+
| [[Canvas Path]] (Shiva) || $SG_SRC/canvas || needs some thinking, probably native OpenVG on RPi <ref>https://github.com/ajstarks/openvg</ref> <ref>http://mindchunk.blogspot.com/2012/09/openvg-on-raspberry-pi.html</ref> or an OpenGL based implementation like nanovg <ref>https://www.raspberrypi.org/forums/viewtopic.php?t=247586#p1516785</ref> James mentioned Skia repeatedly, but that's only an option for Qt-enabled builds obviously.|| {{Pending}}
 
|-
 
|-
 
| [[Effects]] || $FG_ROOT/Effects || not important for the time being, will include [[Shader]]s and probably involve a custom [[Compositor]] pipeline || {{Pending}}
 
| [[Effects]] || $FG_ROOT/Effects || not important for the time being, will include [[Shader]]s and probably involve a custom [[Compositor]] pipeline || {{Pending}}
 
|-
 
|-
| {{readme file|osgtext}} || ... || If you have a chance to replace OSGText by canvas - do so. OSGText (even with the custom OSG repository) does not play nice with our Effects and Shaders framework and will continue to have issues for all eternity.<ref>https://forum.flightgear.org/viewtopic.php?f=37&t=36287&p=353351&#p353351</ref><ref>https://sourceforge.net/p/flightgear/codetickets/2199/#f702</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/37042476/</ref>|| {{Pending}}
+
| [[OSGText Issues]] || ... || If you have a chance to replace OSGText by canvas - do so. OSGText (even with the custom OSG repository) does not play nice with our Effects and Shaders framework and will continue to have issues for all eternity.<ref>https://forum.flightgear.org/viewtopic.php?f=37&t=36287&p=353351&#p353351</ref><ref>https://sourceforge.net/p/flightgear/codetickets/2199/#f702</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/37042476/</ref>|| {{Progressbar|10}}
 
|}
 
|}
  

Navigation menu