In principle, it should be possible to write a scope that exposes the Chrome DevTools protocol. The headless_shell example C++ app (https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md#usage-as-a-c_library) already does this over a local port, but it should be possible to adapt it to Kaleido's architecture where requests are sent as JSON bundles to standard-in and responses are read as JSON bundles from standard out.
For more info on Kaleido's architecture, and the benefits of this approach, see the announcement post (https://medium.com/plotly/introducing-kaleido-b03c4b7b1d81) or this repo's README.
Would this make it possible to eventually use Kaleido as a zero-dependency backend for pyppeteer/puppeteer? If so, this would open up a huge range of additional use-cases.
In principle, it should be possible to write a scope that exposes the Chrome DevTools protocol. The
headless_shellexample C++ app (https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md#usage-as-a-c_library) already does this over a local port, but it should be possible to adapt it to Kaleido's architecture where requests are sent as JSON bundles to standard-in and responses are read as JSON bundles from standard out.For more info on Kaleido's architecture, and the benefits of this approach, see the announcement post (https://medium.com/plotly/introducing-kaleido-b03c4b7b1d81) or this repo's README.
Would this make it possible to eventually use Kaleido as a zero-dependency backend for pyppeteer/puppeteer? If so, this would open up a huge range of additional use-cases.