canvas2svg VS BrowserBox

Reminds me of https://github.com/gliffy/canvas2svg at a different level of abstraction.

I believe PDF.js incorporated some form canvas2svg to try and get a SVG backend working which would allow high resolution printing to PDF but not sure where that's at. I believe printing through PDF.js is blurry due to memory constraints since with normal canvas pdf pages just end up as bitmaps sent to the printer.

SVG ends up staying vector through Chromiums print pipeline resulting in much less memory usage while having much higher dpi final output. I would imagine this is due to SVG being turned into Skia drawing commands that end up as PDF that then gets printed through PDFium?

I used JavaScript to generate planetary positions and orbit paths as SVG with canvas2svg by following this for the mathematical side https://ssd.jpl.nasa.gov/planets/approx_pos.html

Canvas2SVG - I have a feeling I'll get to know this library well someday. Apache Batik - I used it quite a bit in the early days but it never took root in my toolchain. SVGJS It offers compelling shortcuts, I'm just a fan of vanilla JS. This also goes for SNAP SVG

Hey HN! Today, we're proud to introduce BrowserBox Pro, a powerful tool for businesses seeking a secure and reliable browser automation solution for RPA, testing, and more. Our goal is to provide an exceptional product that meets your corporate needs while supporting the ongoing development of BrowserBox.

BrowserBox Pro (Polyform): https://github.com/dosyago/BrowserBoxPro

BrowserBox (AGPL): https://github.com/dosyago/BrowserBox

Why choose BrowserBox Pro?

Enhanced Security: BrowserBox Pro is built with advanced security features, providing an isolated browsing environment to protect sensitive data and ensure secure online interactions.

Powerful Automation: Our solution simplifies RBI, RPA and testing processes, offering seamless integration with your existing workflows and saving you time and resources.

Customization & Scalability: BrowserBox Pro is designed to be flexible and adaptable, catering to a variety of use cases and scaling effortlessly as your business grows.

Dedicated Support: We offer comprehensive documentation and timely support, ensuring your team has the resources needed to maximize BrowserBox Pro's potential.

Continued Innovation: By licensing BrowserBox Pro, you contribute to the ongoing development and improvement of both BrowserBox and BrowserBox Pro, ensuring a cutting-edge product that evolves with your needs.

Open Source Commitment: We're thrilled to announce that BrowserBox is now open source under the AGPL license. This enables a strong community around the project, encourages contributions, and ensures transparency in its development. We believe in giving back to the community while offering a robust and secure solution for businesses through BrowserBox Pro.

We invite you to explore BrowserBox Pro and experience the benefits firsthand. If you're interested in learning more or discussing licensing options, please don't hesitate to reach out to us at [email protected]

Thank you for your interest, and we look forward to helping you revolutionize your browser automation experience!

I recently used Ruffle [2] to get some Flash applications [0] working in the Pro version of my web browser [1], which is specifically designed to be remotely accessible and embeddable in an iframe. To run Ruffle on pages that require it, I utilize the Chrome Remote Debugging Protocol [3], similar to how a Chrome extension content script operates. Ruffle itself relies on WebAssembly and runs smoothly. It's been exciting to see the audio and video functionality of these old games restored and being able to play them again.

-

[0]: https://github.com/ruffle-rs/ruffle/wiki/Test-SWFs

[1]: https://github.com/crisdosyago/BrowserBox#bb-pro-vs-regular-...

[2]: https://github.com/ruffle-rs/ruffle

[3]: https://chromedevtools.github.io/devtools-protocol/tot/