31–40 of 91 posts
How is it different from jimp? https://jimp-dev.github.io/jimp/ Maybe there are some killer features?
That's not necessarily better or worse, it's just potentially helpful if you've got lots of Canvas-based code lying around you want to run outside a browser environment.
Is it a fork of Skia?
Does it depend on Skia?
Did somebody look at a design diagram of Skia and redo the whole thing from scratch?
Did they read about Skia in a blogpost and get the gist of it?
Huh, it's more than just a rendering API: "can render to windows using an OS-native graphics pipeline and provides a browser-like UI event framework". They could add wgpu to get WebGPU support and ANGLE to get WebGL support.
Out of curiosity, what's the use for such library? If you are on a desktop surely there is a better native library to draw shapes, no?
What does "based on Skia" actually mean? Is it a fork of Skia? Does it depend on Skia? Did somebody look at a design diagram of Skia and redo the whole thing from scratch? Did they read about Skia in a blogpost and get the gist of it?
Out of curiosity, what's the use for such library? If you are on a desktop surely there is a better native library to draw shapes, no?
Out of curiosity, what's the use for such library? If you are on a desktop surely there is a better native library to draw shapes, no?
We also need to generate vector PDFs serverside — so we use a node library that speaks the HTML Canvas API and can generate PDFs. This way the result is exactly the same as the rendered sheet music in the web browser. Nice!
The upshot is: this kind of library allows for code reuse in non-browser contexts.
Out of curiosity, what's the use for such library? If you are on a desktop surely there is a better native library to draw shapes, no?
At Soundslice, we have a custom sheet-music-rendering graphics library in frontend JavaScript/Canvas. We also need to generate vector PDFs serverside — so we use a node library that speaks the HTML Canvas API and can generate PDFs. This way the result is exactly the same as the rendered sheet music in the web browser. Nice! The upshot is: this kind of library allows for code reuse in non-browser contexts.
Earlier quoted context omitted.
Canvas is one of the easiest browser APIs to implement because most of it maps 1:1 to PostScript-style 2D APIs. It was created by Apple as a wrapper for CoreGraphics back around Mac OS X Tiger 10.4. (IIRC, Canvas even debuted in Apple's Dashboard widgets rather than Safari? I'm not 100% sure.) I remember writing my own Canvas implementation around 2008-2009 using JavaScriptCore and CoreGraphics. It took maybe two day…
I'd love to learn more about how your 2 day implementation did fillText (incl full unicode rendering, proper text shaping etc)
Also since this was a video application running custom scripts written specifically for that host app, there wasn't a big worry about exact compatibility with any other Canvas-using code.
Anyway, here's the old code that doesn't look like there's anything interesting going on:
https://github.com/pojala/lacqit/blob/main/Lacqit/LQJSBridge...
Looks like I misremembered — it's using Cairo rather than CoreGraphics. I don't remember why that was.
Out of curiosity, what's the use for such library? If you are on a desktop surely there is a better native library to draw shapes, no?
I would imagine that you could use it to write automated tests for Canvas code (maybe charts?) running in Node, e.g., jest with snapshots.