Unifying the 2D rendering backend via canvas: Difference between revisions

Unifying the 2D rendering backend via canvas (view source)

125 bytes removed , 31 December 2022

m

20,741

edits

@@ Line 11: / Line 11: @@
 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.
+Almost every feature in fg needs a maintainer.
    |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=221132#p221132
       |title=<nowiki>Re: Orbital Makes the Sky Black</nowiki>
@@ Line 29: / Line 29: @@
-{{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 contrast 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.
 With the Canvas system every type of widget would be possible, so that also things like submenus can be realized.