userscript-youtube-playlist-o VS GoJS, a JavaScript Library for HTML Diagrams

A silly userscript [1] that uses jQuery selectors to interact with YouTube's DOM to help me move videos around my playlists. Sadly it breaks every few months whenever YouTube updates their DOM. AFIK this is the only way to "programmatically" move videos out of my Watch Later list since they removed the functionality from the API

[1] https://github.com/Trinovantes/userscript-youtube-playlist-o...

I've created a couple of userscripts (anybody remember Greasemonkey?) to help augment sites that I use everyday

https://github.com/Trinovantes/userscript-github-repository-...

https://github.com/Trinovantes/userscript-youtube-playlist-o...

Sadly they break every couple of months when the sites' DOM changes. The YouTube one is currently broken and I haven't had the time to fix it yet

GoJS might work for you: https://gojs.net

Although the focus of the library is interactivity and not setting up sequences of animation, but that is possible too.

My livelihood has been primarily building a Canvas diagramming library since 2010 (https://gojs.net), if anyone has any questions about 2D Canvas use in the real-world I'd be happy to answer them.

roundRect is great. Though you don't need 4 arcTo in order to make a rounded rect, you can use bezier instead (we do). Their example is also 1% amusing because they set the `fillStyle` but then call `stroke` (and not `fill`). I'll have to do some performance comparisons, since that's the operative thing for my use case (and any library author).

text modifiers are very welcome. It's crazy how annoying measuring still is, especially if you want thinks to look perfectly consistent across browsers. Though the chrome dominance is making things easier in one way, I guess.

context.reset is kinda funny. Most high-performance canvas apps will never want to use it. For that matter you want to set all properties as little as possible, especially setting things like context.font, which are slow even if you're setting it to the same value. (Or it was, I haven't tested that in several years).

I'm sure most users know this by now, but generally for performance the fewer calls you make to the canvas and the context, the beter. This is even true of transforms: It's faster to make your own Matrix class, do all your own matrix translation, rotation, multiplication, etc, and then make a single call to `context.setTransform`, than it is to call the other context methods.

I have some problem with gojs(https://gojs.net/),

I'm not the only developer but I made (and still make) GoJS, an interactive diagramming library for the web.

https://gojs.net

Most of its popularity is with large companies building their own internal tools where they need diagramming visualization capabilities (layouts, save/load, undo/redo, data binding, etc). So you won't see it too often in the wild, but under the surface it's used in every industry.

I love it, and I love HTML Canvas, which I wish was more popular.

I actually make a diagramming library for the web, called GoJS: https://gojs.net

So I make all kinds of diagrams, mostly as demonstrations. When developing an API itself, especially one where there are phases (objects must measure themselves and draw in a certain order, and not more than they need to), state machine-style and flowchart-style diagrams are awfully helpful.

GoJS