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-state

v1.0.0

Published

Saves WebGL context state

Downloads

346,876

Readme

gl-state

Preserves WebGL state variables using a stack. This gives similar capabilities to OpenGL 1.0's pushAttrib/popAttrib, only with finer control over the variables which are stored. These methods are useful when writing simple hierarchical rendering functions, or for debugging operations in the middle of the pipeline.

Example

var shell = require("gl-now")()
var createStateStack = require("gl-state")

var stack

shell.on("gl-init", function() {

  //Create stack for saving state
  stack = createStateStack(shell.gl)

  //Push variables onto stack here
  stack.push()
  //... clobber stuff here ...
  shell.gl.clearColor(1, 0, 1, 0);

  //Context states can also be nested
  stack.push()
  // ... clobbber more stuff
  shell.gl.clearColor(0, 1, 0, 1)
  stack.pop()

  //Color back to previous value
  console.log(shell.gl.getParameter(shell.gl.COLOR_CLEAR_VALUE))

  //Restore state
  stack.pop()

  //Now state is completely restored
})

Install

npm install gl-state

API

Constructor

var stack = require("gl-state")(gl[, variables])

Constructs a new state stack object that saves some subset of the global WebGL state for the context gl

  • gl is a WebGL context
  • variables is an optional list of state variables as defined in the specification of gl.getParameter. If not specified, the entire state will be saved

Returns A new WebGL state stack object

Note on performance Modifying the WebGL state is expensive, especially if you update more of it. In general, you should avoid creating too many full context state changes. To do this, you should only specify a list of variables which you plan on actually modifying in the course of your code. For example, to save only state variables associated with the depth buffer, you could do the following:

var depthStack = createStack(gl, [
  gl.DEPTH_CLEAR_VALUE,
  gl.DEPTH_RANGE,
  gl.DEPTH_TEST,
  gl.DEPTH_WRITEMASK
])

In this way you don't have to save and update more of the WebGL context than is necessary.

Note on textures Also the texture unit state is handled in a slightly different way. To specify saving the texture state, you can do:

var textureStack = createStack(gl, [
  gl.TEXTURE,
  gl.ACTIVE_TEXTURE
])

This will save the texture state associated to all currently active texture units.

Note on support Currently support for saving the state of shaders, uniforms and attributes is somewhat limited. If you are using these features and want to preserve the state of the rendering context you must do this yourself.

Methods

The following methods are exposed by the stack object:

stack.push()

Saves the current state of the WebGL context onto the stack

stack.pop()

Restores the last pushed state from the stack.

Credits

(c) 2014 Mikola Lysenko. MIT License