npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

gl-post

v1.0.1

Published

Simple WebGL post-processing

Downloads

32

Readme

gl-post

Simple WebGL post-processing using some pieces from stackgl.

check out the demo.

Usage

NPM

See the example code for a full usage example.

post = glPost(gl, shader, opts={})

Creates a new post-processing instance, where gl is a WebGLContext instance and shader is a shader instance from either gl-shader-core or glslify.

The vertex shader is supplied for you, and available at gl-post/post.vert. The shader you pass in may also be a function that takes a WebGLContext and returns a shader instance too, so the following is valid:

var glslify = require('glslify')
var glPost  = require('gl-post')

post = glPost(gl, glslify({
    vert: 'gl-post'
  , frag: './src/my-shader.frag'
}))

There are also a few options you can include too:

  • minFilter: the texture minification filter to use. Defaults to gl.LINEAR.
  • magFilter: the texture magnification filter to use. Defaults to gl.LINEAR.
  • colorBufferName: the name of your color buffer uniform to use in your shader. Defaults to colorBuffer.

In simple cases, you'll want to do something like this:

var glslify = require('glslify')
var glPost  = require('gl-post')

post = glPost(gl, glslify({
    vert: 'gl-post'
  , frag: './src/my-shader.frag'
}))

function render() {
  post.bind()

  // Note that it's important you clear your
  // depth/color buffers for this to work properly :)
  gl.clear(gl.COLOR_BUFFER_BIT | gl.DEPTH_BUFFER_BIT)
  gl.viewport(0, 0, canvas.width, canvas.height)

  // ...draw your scene to the framebuffer here...

  post.draw()
}

post.shader

The shader you gave gl-post will also be exposed here, for quickly changing uniform variable values.

post.bind()

Starts drawing to the post-processing buffer. Anything you do now will not be immediately drawn to the screen, but instead drawn to an off-screen framebuffer for you to draw later using the post-processing shader.

You should this when you're ready to start drawing your scene.

post.draw()

Draws the framebuffer to the screen using your shader, returning your drawing power to the screen in the process.

post.unbind()

Call this if you want to explicitly disable rendering to the framebuffer before drawing to the screen.

License

MIT. See LICENSE.md for details.