3 ms·
Well I'm surprised I haven't seen it yet, but I'm using Google Caja[0] for my own side project[1] (which, actually, I haven't touched in a while..) This allows
by lwansbrough 7y ago
Well I'm surprised I haven't seen it yet, but I'm using Google Caja[0] for my own side project[1] (which, actually, I haven't touched in a while..) This allows plugin developers to create fully custom HTML plugins that run in the same frame (which is crucial for AudioNodes to be operated on by multiple plugins in my case.) Example of a plugin: https://github.com/lwansbrough/attack/blob/master/src/plugins/push2-test.html https://github.com/lwansbrough/attack/blob/master/src/plugin...
Actually my demo goes as far as showing how one plugin can register a resource that is then used by another plugin. In this case I developed a plugin which registers a high level interface for access to an Ableton Push 2 device, and then another plugin uses that interface to draw to the Push's display using the canvas API. https://twitter.com/lwansbrough/status/1125842014128312320 https://twitter.com/lwansbrough/status/1125842014128312320
[0] https://github.com/google/caja https://github.com/google/caja
[1] https://github.com/lwansbrough/attack/blob/master/src/areas/daw/components/plugin/Plugin.vue https://github.com/lwansbrough/attack/blob/master/src/areas/...
- anamexis 7y agoThat is super cool!
- lwansbrough 7y agoThanks! And of course Caja is to thank for a large part of the major technical hurdles.
- cxr 7y agoCaja was started at Google under Mark S. Miller, and it's the predecessor to Agoric's current sandboxing work, which is what Figma is using here.
- lwansbrough 7y agoInteresting. I guess what is missing from the sandbox described in the article is the HTML/CSS component.