Template:Affected by Compositor: Difference between revisions
m (add placeholder logo taken from: Compositor) |
mNo edit summary |
||
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 [[Changelog 2020.2|2020.2]] (6/2020). Please see: [[ {{{1| | | <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.2|2020.2]] (6/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:Compositorflagship.png|thumb]] | | valign="top" | [[File:Compositorflagship.png|thumb]] |
Revision as of 09:38, 26 May 2020
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.2 (6/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 . talk page. |
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.2 (6/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 . talk page. |
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.2 (6/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 . talk page. |