Shader Node system improvements

[rickard]

Yeah. It seems it was not what I thought it was.

[Ali_RS]

From what I recall Nehon plan was to write a Java API to create shader nodes via code then a visual editor could be created upon this API. Some folks here may have more info on this so.

[oxplay2]

yes, sounds logic. Java API is there as i see, but probably no editor were done.

[pspeed]

@oxplay2

but probably no editor were done.

There is a visual editor. See other thread.

[oxplay2]

but there is no TestShaderNodesModifApi.java in master.

See other thread.

can you link which one you mean?

[Ali_RS]

I found the original post by Nehon:

Thoughts on Shader Nodes

I’ve been thinking of several enhancements for Shader Nodes and I’d like shader nodes users to chime in. There are a lot of nice things about the Shader Nodes system, but other things that are not so great. My main concern is that they can be really cumbersome to write, because they are described in a very declarative way. Without a proper visual editor it’s frankly easier to code a good old shader from scratch than making a shader node based material definition. And since there is no officia…

Edit:
Would be cool if someone can go ahead and finish this idea

Edit2:
You can follow his work in this branch:

GitHub - jMonkeyEngine/jmonkeyengine at shader-nodes-enhancement

[rickard]

Here is the thread about the Shader Editor:

Question about Shader Editor

Hi everyone, I’m happy with the new initiatives that are coming out. I hope you will soon find a solution to easily maintain and evolve the SDK. I did some other tests. The tool to create new Shader Nodes does not work. [create-shader-node] Nothing happens when you click on the Next button. [create-shader-node-2] No problem, I created an empty file and named it PBRLighting.j3sn. Next step. I wrote a prototype template: ShaderNodeDefinitions{ ShaderNodeDefinition PBRLighting { …

[Ali_RS]

oxplay2 means, there is no editor done over the API proposed by Nehon. Not any, many, every other editor.