Related to #36

Including basics of building the bundle Frogasaurus-style.
And where to put specific bits of code, eg: exports, globals, etc

Linked with #36

When you try to use habitat in a web worker, it has issues because of document

if you make from something other than zero, it still tweens from zero, and other stuff goes weird

The tween function has lots of good functionality now. It has grown to be more complicated. Maybe we could try to simplify it down into smaller pieces. The one function does a few different things:

• An extremely simple tween (using launch and land options)
• Named eases from easings.net
• Manually provided easing functions

Here's a wishlist I would have:

• Can the easings.net functions be modifiable with the launch/land values too?
• If the above checkbox is possible, then we could get rid of the basic 'launch' and 'land' ease, and just make one of the easings.net the default.
• I wonder if the easings.net things could just be refined down to the ones that just ease in and out, so that the list is smaller. (as long as the above checkbox is possible).
• I feel like all the in-built easings.net functions should be functions on the Tween object, like Tween.EASE_IN_CIRCULAR or something. Then the tween function would only do one thing: accept an ease function. No strings, or default launch/land behaviour.

Those are my loose + messy thoughts!

I hate trigonometry. I can't even spell it.

I want some helper functions that use non-maths language to help me out.

https://github.com/TodePond/Habitat/blob/main/libraries/habitat-import.js#L1148-L1151

It would be handy to have a version of Colour.make that doesn't do all the heavyweight calculations of the current one. Sometimes you wanna make colours on the fly, and the current one is very slow.

It would be useful if Colour objects had named rgb properties

eg: Random.from isn't there

There should be a rough guide for the principles/goals/style of the Habitat library, so that it is easier for people (including me) to contribute to the library!

This would make editing/adding to Habitat a lot easier

Add the TodePond colours maybe? Or should it be in its own repo?

(instead of a string literal)

It's annoying to use in its current state!

This breaks habitat-import.js

It would be great to have a function that turns webassembly text format into native code.

eg: Array.prototype.shuffle() -> shuffleArray(array)

• Array
• Async
• Colour
• Console
• Document
• Event
• Habitat
• HTML
• JavaScript
• Keyboard
• LinkedList
• Math
• Memo
• Mouse
• Number
• Random
• Stage
• String
• Struct
• Touches
• Tween

Optional new while we're at it:

• Lerp
• JSON
• Pointer
• Vector

Make a tween or animate function that lets you gradually change a variable's value over time.

let height = 10
tween(height, {from: 2, to: 8})

I make this construct so often it would be good to make it

There are some issues when making a canvas with the HTML function.

if you don't specify to or from args, then it bugs out

If to and from are the same, it goes wrong

A simple linked list maker would be handy.

I made some little helper functions to help me work with webassembly in my 'Scale' video. It would be useful to have them in the Habitat library.

https://github.com/TodePond/BigPond/blob/93fa001b4bfb0f66e20cc63fe18a0df18a52f983/7c/script.js#L31

Stage does too much in some ways. eg: I don't want it to have its own tick/draw/update functions! However, it does too little in other ways. eg: It doesn't auto-resize, and it doesn't have background colour, or overflow settings, or margin. It should be rewritten so that it focuses more on its HTML and less on its javascript.

the launch and land options do the opposite of what they should.

Function that converts JSX to element(s)

And spoof a React object to hijack the default deno JSX factory

It would be great if there were some functions available for Colour objects that let you adjust brightness/saturation/etc...

Similar to JavaScript and HTML, it would be great to be able to call WebGL somehow.

Colour objects should have read-only hue, saturation and lightness values. Maybe they should be accessible with h, s and l as well.

This issue comes from: #19

There should be a function to cache all splash colours

Colour objects should have read-only cyan, magenta, yellow, and key properties. And maybe c,y,m,k properties too.

This issue comes from: #19

An error appears when you touch the screen. Something's broken.

Copy some stuff over from the ScreenPond code

It messes with the global scope too much. I don't really use it ever anymore. Get rid of it?

It has a special place in my heart though because it's silly. Maybe I should move it (and other silly JS ideas) into their own esoteric project!

Auto function memo-iser

It would be useful to have clamp and wrap functions as I end up remaking them a lot. Not sure if they should just be globals (bold move!?) or like... Math.clamp ?

Object.prototype.values() and similar functions should return an iterable, not an array, so that it has parity with how Map.prototype.values() etc works.

The tween function is messy and dodgy. Redo!

Copy over some stuff from the ScreenPond code

Provide some global state for tracking pointer events, similar-ish to Mouse. Use the opportunity to reconsider Mouse and Touch/Touches because they're a bit clumsy.