Ricky Reusser

I believe it requires the [brfs](https://github.com/browserify/brfs) transform (short for "**br**owserify-**fs**) in order to work. If using browserify it happens automatically [based on these lines in this module's package.json](https://github.com/freeman-lab/control-panel/blob/master/package.json#L31-L33), but if...

Thanks for the PR! It seems pretty straightforward and seems like the right move!

Oh, whoopsie. I'm glad to help get this merged, but looks like I don't have permissions. /ping @freeman-lab 😄 Also, @marcofugaro It might be of interest that I've been working...

No, it doesn't. I wanted to add that, but in my opinion, I would *love* to rewrite this module with, for example, preact, so that you could make the UI...

Ah, interesting… What about keeping a somewhat similar API and using (p)react internally (basically exactly as you described; just internal)? Mainly because exposing react directly either makes it pretty verbose...

Oh, and one other thing is that the values need to overlay the sliders! And the sliders need to work on mobile without trying desperately to hit the 5x5px region...

One last thought is that I often just use it as a single command, which makes for very low mental overhead, e.g.: ```javascript require('control-panel')([ {type: 'number', label: '...'}, ]).on('input', ...);...

Update: I've finally cleaned up my honest stab at this. You can find a short writeup here: https://rreusser.github.io/control-panel-2/ The source lives here: https://github.com/rreusser/control-panel-2 And, naturally: https://observablehq.com/@rreusser/control-panel-2-prototype-test.

I'm going to close this, as there's no plan to resurrect the live editor, and we've all but shut down regl.party and redirected to https://regl-project.github.io . It may not suit...

@DickyT — I'm looking into fixing this issue. Your repo doesn't have an issues page, but the plan is to submit a PR to your repo. Sound good?