Difference between revisions of "Canvas and OpenGL ES"

From FlightGear wiki
Jump to: navigation, search
m (needs some TLC: https://forum.flightgear.org/viewtopic.php?f=14&t=36869&p=361216#p361216)
m
 
Line 1: Line 1:
 +
{{Stub}}
 +
 
{{Portability Navbar}}
 
{{Portability Navbar}}
  
{{Stub}}
 
  
 
The Canvas is a property tree-based subsystem using listeners, the canvas is primarily a wrapper on top of Shiva and OSG that is invoked via listeners.
 
The Canvas is a property tree-based subsystem using listeners, the canvas is primarily a wrapper on top of Shiva and OSG that is invoked via listeners.

Latest revision as of 14:09, 5 February 2020

This article is a stub. You can help the wiki by expanding it.


The Canvas is a property tree-based subsystem using listeners, the canvas is primarily a wrapper on top of Shiva and OSG that is invoked via listeners.

So all the OpenGL code is either located in Shiva or in OSG - OSG can be told to use OpenGL ES. So it would be a matter of experimenting with it.

For this particular project, I would suggest to extract the Canvas into a standalone executable - something like this has been previously done by TorstenD when he came up with FGPanel, he "just" extracted FlightGear's 2D panel code and turned it into a standalone binary. This alone would help us ensure that we can optimize the canvas to support OpenGL ES - once that is working, you could cross-compile the standalone canvas binary. Technically, this will involve some -but not all- of the steps outlined at: FGCanvas

(not all of them, because FGCanvas is eventually intended to be merged back into the main code base)[1]

References

References
  1. Hooray  (Jan 31st, 2014).  Re: TQ/Panel for FG made with Kivy .