20,741
edits
Unifying the 2D rendering backend via canvas: Difference between revisions
Jump to navigation
Jump to search
Unifying the 2D rendering backend via canvas (view source)
Revision as of 19:11, 5 November 2012
, 5 November 2012→Background
| Line 2: | Line 2: | ||
== Background == | == Background == | ||
{{cquote|Moving the HUD to use the Canvas would be a great step from my point of view, since it and 2D panels (which I am happy to write the convert for!) are the last places besides the UI which make raw OpenGL calls, and hence would benefit from moving to the Canvas (and thus, to use OSG internally)|[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38629.html Thomas Geymayer]}} | |||
{{cquote|using the Canvas also for the GUI would give us the advantage of a unified rendering backend for any type of GUI/text rendering and also the ability to use the same widgets everywhere - eg. use them also inside aircrafts for CDU GUIs or other displays... |[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37867.html Thomas Geymayer]}} | |||
{{cquote|I'm even more convinced now that we should move the 2D panel and HUD rendering over to this approach, since that would get rid of all the legacy OpenGL code besides the GUI.|[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37868.html James Turner]}} | |||
{{cquote|The long term idea is to eventually port some other 2D elements to this backend (eg the HUD and 2D panels) so they use OSG (and osgText) natively, and hence reduce the amount of C++ code we have for these jobs. (And increase our chances of working with newer OpenGL versions that forbid old style GL calls) Long-term here means 'after 2.8 at least'.|[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37441.html James Turner]}} | {{cquote|The long term idea is to eventually port some other 2D elements to this backend (eg the HUD and 2D panels) so they use OSG (and osgText) natively, and hence reduce the amount of C++ code we have for these jobs. (And increase our chances of working with newer OpenGL versions that forbid old style GL calls) Long-term here means 'after 2.8 at least'.|[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37441.html James Turner]}} | ||
{{cquote|Moving the HUD to use the Canvas would be a great step from my point of view, since it and 2D panels (which I am happy to write the convert for!) are the last places besides the UI which make raw OpenGL calls, and hence would benefit from moving to the Canvas (and thus, to use OSG internally)|[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38629.html James Turner]}} | |||
<references/> | |||
== Background == | == Background == | ||