Will Bamford

This PR has a performance overhead for non-sticky behaviour so going to park this for now and have a rethink on solution.

We could still detect and publish events on `pinch` and `unpinch` and then it's up for consumers to translate this to `zoom` levels (as per how zoom control buttons work...

Going forward it might also be useful to have the component manage its own state (`setState`) but allow consumers to override. E.g. have default `zoom`, `toggle open` handling etc.

I'm also interested in getting this to work with React Native. So, use RN for the general UI but GLFM for OpenGL visualisations. In this case I wouldn't want GLFM...

Hi @yegor256, not sure why CI build is failing - tests pass for me locally.

Sorry, that's not currently possible. PRs welcome though 😀

Hi all, sorry - missed this thread somehow. I'll put something in the README.

Think you basically have to do something like: ```js const loop = () => { regl.poll() regl.clear({ color: [0, 0, 0, 1], depth: true, }) draw() // your draw commands...

> have separate browser/node interfaces and specify them using the browser field in the package.json Yes, was thinking along the same lines. My fallback for if you didn't like the...

Hey @mikolalysenko, I [forked resl](https://github.com/WebSeed/resl) a few weeks ago with the intention of doing the above, but found it to be not as straightforward as I would have liked -...