Cammy

Fork

Prototype a Cammy-to-JS compilation path.

We are compiling with a stub, as we've done in the past; this time, we
are using PureScript.

Get back up and running.

Hooray for "new" hardware.

Fix tiles for anonymous expressions.

Allow pausing and unpausing videos.

Use Preact ref hooks for canvas access.

This commit includes a measurable portion of boilerplate from
https://stackoverflow.com/a/74258812/264985 and I am very grateful to
this answerer for offering a simple solution.

Finish converting tiles to Preact components.

I still need to rewrite all of the renderers, but now the path for that
is clear and obvious.

Switch to Preact.

Quite a silly reason for switching, but so far it has not been painful.

Factor out the hive.

Also, render functions with domain 2 like domain 1.

Don't render empty trails.

Saves a bit of screen space.

Many animations work in Honey!

deco-circles, red-ellipse, and max-headroom all work! jupiter-storm is
still giving a blank screen, but it seems like the fundamentals are
finally there.

We are currently pegging the CPU at 5 frames/s. I would like to
eventually get to about 20 frames/s.

Switch over to Purescript for core templates.

Sadly, Purescript doesn't seem equipped with the full range of ES types
by default, so we have to bring our own foreign functions.

Rewrite the trampoline in Purescript.

Took a little bit of effort, but it seems worthwhile! The generated code
has the desired loop! I'm impressed.

Allow black-and-white images.

Expand dissolved expressions correctly.

This might be a hack.

Compile anonymous expressions, not just dippers.

First attempt at implementing an animated canvas.

Add some jets for speed.

Stop fucking around with the trampoline for now.

Switch to a free-monad encoding for trampolines.

This is based on the idea that a trampoline monad is like a free monad
for some underlying lazy suspension of pure values.

Deduplicate the parser somewhat.

I think that the RPython codebase is not on the way out, but the Python
3 codebase should be unified.

Switch to a handwritten trampoline.

Use Math.floor() correctly.

Draw a red ellipse on a canvas.

Put borders onto tiles.

Autocomplete possible dippers.

Send types to the browser.

Use Bilby for trampolining.

And suddenly nat/sylvester, list/gauss, nat/sqr, and other curry-heavy
sequences are runnable! Nice.

Partially revert.

Compile pr.

There are some nuances to WASM which I don't really appreciate. But, for
now, we'll just push onward. Next is memory allocation for pairs, tagged
unions, curries, etc.

I guess we're going to write a templating compiler.

It's okay, though; we will be able to optimize the results.