Using the click-drag-rect patterns to add or select objects visually is a staple of graphics UX - this is one way to do it with Konva. The trick is to keep everything relative to the stage. Lets take a look...
After getting a few shapes onto the canvas, folks start wondering about how to make the canvas play nice with their UI and the subject of scrollbars emerges. But Konva does not have automatic scrollbars on a canvas element, so what can we do...
We all know that ES6 introduced template literals via which we can write a string. But there's a catch if the template is a string variable - such as when you have multilingual error messages coming from a database. Is there another way...
So I'm writing various library components using TypeScript that are targeted at Konva and I want the components to be usable in Vanilla JS without being opinionated about where Konva's JavaScript is located. What?
I'm writing a JavaScript lib with TypeScript, using the excellent Vite for on-the-fly transpiling and packaging. This post is about the configuration that I use and specifically covers removal of comments.
Various use cases require the ability to save multiple _frames_ from a canvas as an animated GIF. This isn't something the canvas can do out of the box. Lets dig into how to make it happen...
Brave browser has a sophisticated approach to protect from browser fingerprinting. Unfortunately this makes for problems for legitimate canvas apps. In this post I investigate, try to explain what I found and suggest a work-around.
Someone on the Konva Discord group had an issue loading a complex canvas on mobile via the Konva.Node.create() process. The app works fine on desktop but iPhone Safari is complaining about the canvas being too large. What gives?