Shader injectors

[GoogleCodeExporter]

PDF spec is available on jme_private channel

Original issue reported on code.google.com by ShadowIs...@gmail.com on 24 Sep 2010 at 3:32

• Blocking: #64, #208, #64

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by ShadowIs...@gmail.com on 6 Sep 2012 at 5:31

• Now blocking: #64

[GoogleCodeExporter]

Original comment by ShadowIs...@gmail.com on 6 Sep 2012 at 5:31

• Added labels: Milestone-3.1
• Removed labels: Milestone-3.0-Alpha

[GoogleCodeExporter]

I can't find the spec, could you please upload it on the gdrive?

Original comment by remy.bou...@gmail.com on 28 Dec 2012 at 8:21

[GoogleCodeExporter]

I think the ideas we had lately deviated significantly from what that 
specification proposed.

The current ideas were:
1) A 'shaderlet' system where each one has acceptable inputs and outputs. The 
system would combine shaderlets together by plugging inputs into outputs based 
on identifiers. 
2) Do not implement any shader management system. Just use jME3's built-in 
shader library functionality and create functions that are flexible and can be 
used in many instances.

Original comment by ShadowIs...@gmail.com on 28 Dec 2012 at 7:20

[GoogleCodeExporter]

ok, i'm trying to brush up an hypothetical system based on 1. currently it just 
a doc, i'm trying to write things down, and i'll submit it to the team before I 
start to implement things. 

Original comment by remy.bou...@gmail.com on 28 Dec 2012 at 7:24