Resource:Shadermanager: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Resource page}} | {{Resource page}} | ||
{{Warning|This is a <em>planned</em> resource (it's not ready yet!)|true}} | |||
Shadermanager is a <em>planned</em> resource to facilitate the managment of shaders in MTA, analogous to mapmanager for maps. This page is simply here to serve as a place to share the proposed system. To discuss, contact [[User:John|John]] on #mta. | Shadermanager is a <em>planned</em> resource to facilitate the managment of shaders in MTA, analogous to mapmanager for maps. This page is simply here to serve as a place to share the proposed system. To discuss, contact [[User:John|John]] on #mta. | ||
Revision as of 01:38, 29 April 2012
|
Warning: This is a planned resource (it's not ready yet!) |
Shadermanager is a planned resource to facilitate the managment of shaders in MTA, analogous to mapmanager for maps. This page is simply here to serve as a place to share the proposed system. To discuss, contact John on #mta.
Proposed Features
- Adoption of a "type='shader'" standard to allow shadermanager to find all the shaders on a server.
- Minimalistic GUI to allow for the enabling/disabling of shaders.
- Small log to allow for viewing of shader-specific errors.
- Exported functions to allow shadermanager to function as a backend for other scripts (allowing someone else to implement their own GUI, for example).
- getShaderFromName, getAllShaders, setShaderEnabled, isShaderEnabled, isShaderCompatibleWithClient
- Adoption of certain exported functions for shaders to allow shadermanager to control all the shaders on a server.
- setShaderEnabled, isShaderEnabled