Template:Affected by Compositor: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(to be used to update articles that will become obsolete due to the implementation and integration of the Compositor framework)
 
No edit summary
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
{| class=toccolours align="center" style="text-align: center; width: 80%; font-size: 85%; clear:both; margin-top:1em; margin-bottom:-0.5em; border-left: 15px solid orange;"
{| class=toccolours align="center" style="text-align: center; width: 80%; font-size: 85%; clear:both; margin-top:1em; margin-bottom:-0.5em; border-left: 15px solid orange;"
| <big>'''IMPORTANT: Some, and possibly most, of the features/ideas discussed below are likely to be affected, and possibly even deprecated, by the ongoing work on providing a property tree-configurable rendering pipeline accessible via XML using the new [[Compositor]] system available since FlightGear 2020.1 (6/2020). Please see: [[ {{{1|Compositor}}} ]] for further information'''</big>
| <big>'''IMPORTANT: Some, and possibly most, of the features/ideas discussed below are likely to be affected, and possibly even deprecated, by the ongoing work on providing a property tree-configurable rendering pipeline accessible via XML using the new [[Compositor]] system available since FlightGear [[Changelog 2020.3|2020.3]] (11/2020). Please see: [[ {{{1|Post FlightGear 2020.2 LTS changes}}} ]] for further information'''</big>
''You are advised not to start working on anything directly related to this without first discussing/coordinating your ideas with other FlightGear contributors using the FlightGear developers mailing list or the {{forum link|f=47|title=Effects & Shaders}}.  [[Talk:{{PAGENAME}}|talk page]].''
''You are advised not to start working on anything directly related to this without first discussing/coordinating your ideas with other FlightGear contributors using the FlightGear developers mailing list or the {{forum link|f=47|title=Effects & Shaders}}.  [[Talk:{{PAGENAME}}|talk page]].''
| valign="top" | <!--[[File:Canvasready.png]] need a compositor logo ?-->
| valign="top" | [[File:Compositor logo.png|300px]]
|}<includeonly>{{main other|[[Category:Affected by Canvas]]}}</includeonly><noinclude>
|}<includeonly>{{main other|[[Category:Affected by Compositor]]}}</includeonly><noinclude>
{{Informative template|1=
{{Informative template|1=
__NOTOC__
__NOTOC__

Revision as of 08:25, 1 January 2021

IMPORTANT: Some, and possibly most, of the features/ideas discussed below are likely to be affected, and possibly even deprecated, by the ongoing work on providing a property tree-configurable rendering pipeline accessible via XML using the new Compositor system available since FlightGear 2020.3 (11/2020). Please see: Post FlightGear 2020.2 LTS changes for further information

You are advised not to start working on anything directly related to this without first discussing/coordinating your ideas with other FlightGear contributors using the FlightGear developers mailing list or the Effects & Shaders subforum This is a link to the FlightGear forum.. talk page.

Compositor logo.png
The following template description is not displayed when the template is inserted in an article.

Goal

This template can be used on top of pages related to projects that will be affected or obsoleted by the development of the new Compositor, FlightGear's fully XML/property-configurable rendering framework.

Adding this template to a page in the article namespace will automatically add Category:Affected by Compositor to that page.

Usage

Put this template on top of the page.

{{Affected by Compositor|alternate page}}
alternate page
Optional alternate Compositor related page pointed to for further information (such as e.g. MapStructure or NavDisplay, defaults to Compositor.

Examples

Using no parameters

{{Affected by Compositor}}
IMPORTANT: Some, and possibly most, of the features/ideas discussed below are likely to be affected, and possibly even deprecated, by the ongoing work on providing a property tree-configurable rendering pipeline accessible via XML using the new Compositor system available since FlightGear 2020.3 (11/2020). Please see: Post FlightGear 2020.2 LTS changes for further information

You are advised not to start working on anything directly related to this without first discussing/coordinating your ideas with other FlightGear contributors using the FlightGear developers mailing list or the Effects & Shaders subforum This is a link to the FlightGear forum.. talk page.

Compositor logo.png

Linking to an alternate page

{{Affected by Compositor|Foo}}
IMPORTANT: Some, and possibly most, of the features/ideas discussed below are likely to be affected, and possibly even deprecated, by the ongoing work on providing a property tree-configurable rendering pipeline accessible via XML using the new Compositor system available since FlightGear 2020.3 (11/2020). Please see: Foo for further information

You are advised not to start working on anything directly related to this without first discussing/coordinating your ideas with other FlightGear contributors using the FlightGear developers mailing list or the Effects & Shaders subforum This is a link to the FlightGear forum.. talk page.

Compositor logo.png