20,741
edits
Unifying the 2D rendering backend via canvas: Difference between revisions
Jump to navigation
Jump to search
m
Unifying the 2D rendering backend via canvas (view source)
Revision as of 17:16, 4 January 2015
, 4 January 2015→Background
No edit summary |
m (→Background) |
||
| Line 9: | Line 9: | ||
== Background == | == Background == | ||
{{FGCquote | |||
| the reason we still havent moved to opengl 3.x+ has been due to supporting OSX. If we wish to support OSX, we need to completely abandon the fixed function pipeline. Some of our dependencies (plib) are no longer maintained , so must be replaced with something that supports shaders (canvas, etc). <br/> | |||
<br/> | |||
Apple has made app developers to move on or stay in fixed fn. We aren't there yet.<br/> | |||
<br/> | |||
Almost every feature in fg needs a maintainer. Maybe someone who especially loves deferred rendering will step up, and begin migrating Thorsten's als shaders to rembrandt. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=221132#p221132 | |||
|title=<nowiki>Re: Orbital Makes the Sky Black</nowiki> | |||
|author=<nowiki>psadro_gm</nowiki> | |||
|date=<nowiki>Sat Oct 18</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | |||
|the other issue is that there's still legacy GL code running in the main/rendering loop that prevents us from using a more recent OpenGL version, such as the panel/HUD and GUI code - those things are in the process of being unified, and re-implemented, on top of modern OSG code using a shared back-end via Canvas. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=221133#p221133 | |||
|title=<nowiki>Re: Orbital Makes the Sky Black</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sat Oct 18</nowiki> | |||
}} | |||
}} | |||
{{cquote|In contrary to using some hardcoded GUI system (PUI, osgWidget, etc.) this approach would give much more flexibility and also the means of modifying and creating new widgets without the need to touch any core code. | {{cquote|In contrary to using some hardcoded GUI system (PUI, osgWidget, etc.) this approach would give much more flexibility and also the means of modifying and creating new widgets without the need to touch any core code. | ||