pex-gl / pex-next Goto Github PK

E.g. sattelite.js or glsl-fxaa as they can't be browserified.

Nice info here about porting http://www.shaderific.com/blog/2014/3/13/tutorial-how-to-update-a-shader-for-opengl-es-30

When installing non existing module there is no page reload and no error or warning.

The server doesn't crash though.

Currently considering multiple approaches:

1 - Low level intermediate mode (kind of stack-gl-ish, but also more like Foam)
https://github.com/vorg/pex-next/blob/master/00-core/basic.js

• more control but also more boilerplate
• less hidden state
• no automagic

2 - Game-engine / Vulkan / Metal like command oriented renderer
https://github.com/vorg/pex-next/blob/master/01-draw-command/basic.js

• more functional / data driven
• potentially easier to optimize (state switching, batching)

3 - Even more OOP? SceneGraph?

Standard https://github.com/feross/standard

• two spaces
• no semicolons
• automatic formatting and checking (via modules)

Example file: https://github.com/feross/bittorrent-dht/blob/master/client.js#L1

I'm working on ShaderProgram abstractions that right now are not very tied to any particular framework. They are like gl-shader but with a bit more focus on modularity, simplicity, performance and developer UX.

• core: https://github.com/mattdesl/glo/blob/dev/src/shader/index.js
• extract uniforms/attribs: https://github.com/mattdesl/gl-shader-extract
• reflection: https://github.com/mattdesl/glsl-extract-reflect to avoid strings for arrays/structs

var shader = createShader(gl, { vertex: '...', fragment: '...' })

//use program
shader.bind()

//gl.uniform1f
shader.uniforms.lights[0].radius(2)

//gl.getUniform
var radius = shader.uniforms.lights[0].radius()

//set explicit locations, to be used with VAO extension
shader.reload({ vertex: ..., fragment: ..., attributes: [ { name: 'uv', location: 2 } ])

"object object object object..." 10'000 times