html2svg
canvas2svg
| html2svg | canvas2svg | |
|---|---|---|
| 2 | 3 | |
| 1,175 | 671 | |
| - | 1.3% | |
| 0.0 | 0.0 | |
| 5 months ago | 6 months ago | |
| TypeScript | JavaScript | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
html2svg
-
Forking Chrome to Turn HTML into SVG
I've opened an issue to track PDF support [0], you can subscribe to get progress updates for this specific feature. For general project updates you can use the "Watch" button on the repository to get commit updates on your feed.
[0] https://github.com/fathyb/html2svg/issues/3
-
Forking Chrome to turn HTML into SVG
The codebase for html2svg is very simple and building is done using 4 commands. It uses Electron.js, which in itself is a fork of Chromium with all the build infrastructure to apply patches dynamically. I'm preparing merge requests to submit all changes in skia.patch to the upstream. If all are accepted, we'll only need ~200 lines patched in Chromium.
canvas2svg
-
Forking Chrome to Turn HTML into SVG
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?
-
Snapshot of planetary positions at a given date. Custom code, 10 tool changes, plotted on a 3D printer.
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
-
Essential SVG tools
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
What are some alternatives?
BrowserBox - 📷 BrowserBoxPro - The internet. But unrestricted. And secure. Remote browser isolation product, available here and in Pro for purchase on our website. [Moved to: https://github.com/dosyago/BrowserBoxPro]
resvg - An SVG rendering library.
svg2pdf.js - A javascript-only SVG to PDF conversion utility that runs in the browser. Brought to you by yWorks - the diagramming experts
imagetracerjs - Simple raster image tracer and vectorizer written in JavaScript.
satori - Enlightened library to convert HTML and CSS to SVG
svg_crop - Remove blank space from around any SVG instantly.
lib2geom
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Automaton - Reactive State Machine Framework for Arduino
socr - screenshot OCR server
svgcleaner - svgcleaner could help you to clean up your SVG files from the unnecessary data.