Working with mouse and touch events is one of the biggest challenges for me in making interactive web apps. The availability of pointer events helps a lot, but I still pretty quickly end up with a mess of conditionals that are hard to reason about. I'm working on some new strategies and abstractions to help with this.

PointerOne, PointerTwo, PointerThree

The pointer event API provides events for pointerDown, pointerMove, and pointerUp. Using the pointerId provided you can link those events together into a continuous Pointer object that contains the whole lifecycle. I put this together into a SubPointer class.

Refactored and got area selection working. Though what area selection should do in a 3D-ish environment turns out to be a whole thing.

Exploded.

Could probably do some pretty questionable data visualization with this.

Expand.

I'm possibly in the midst of revising a bunch of my assumptions about how I like to code projects, so I wanted to write down my current thoughts. I'm probably in a honeymoon phase with the new set-up, so it's possible as I work longer I'll run into a bunch of walls and complications and end up re-revising.

Typescript

I have been avoiding trying Typescript, but I've now seen too much work from people working on involved interfaces (mainly Steve Ruiz's work and the Excalidraw project) to justify not at least trying it. So I've been trying it on the new prototype and I think I like it. Barring running into some tremendous catch, I think I'll use it from here on out.

Reworking corner resize (and many other things).

Sampling.

Refactored to get multiple dsts per src working along with resize.

Eliss - I played this game a fair amount and have been thinking about it a lot lately in relation to multi-touch.

From: https://en.wikipedia.org/wiki/Eliss

Asteroids vibe.

I think this color set-up of background, foreground and highlight could be a good fit for some future projects.

From: https://kool.tools/bipsi/user-guide.pdf

Still pretty weird.

From: https://portal.constraint.systems

Pretty weird.

More boxes.

More portal work.

The idea

Get a storefront, split it into a front half and a back half. Put six computers in each half. The front half is free for anyone to come and use. The catch is that the free-to-use computers only run the software made in the lab by the in-residence developers that work in the back half.

Things to consider

Boxes.

I think I need to turn recursion off for this project. To be returned to later.

Portal.