Compositor: Difference between revisions

Jump to navigation Jump to search
626 bytes added ,  30 November 2019
m
Line 120: Line 120:


=== Runtime Toggling ===
=== Runtime Toggling ===
drop support for legacy renderer: agree - not wise.  It is too early to
consider doing so.  Ideally, we would want a toggle between Default and
Compositor pipelines while Compositor is being developed.  I would keep
the toggle point very simple for now - perhaps a commandline switch to
activate compositor and disable default.  The harder part is the
refactoring necessary to allow the two approaches to coexist - one being
active and the other being inactive (e.g. feature toggle -
https://www.martinfowler.com/articles/feature-toggles.html) <ref>https://sourceforge.net/p/flightgear/mailman/message/36657761/</ref>
Runtime toggling for the Compositor has been discussed before.
Runtime toggling for the Compositor has been discussed before.
Implementing such thing is not trivial though. The legacy
Implementing such thing is not trivial though. The legacy

Navigation menu