Alex Komoroske

Allow multiple configs

3

In URL, the filename should be `/FILENAME/sim-name/round-number/frame-number/`, where FILENAME is looked for at `/config/FILENAME.json`

A way for people to save and share specific configurations

2

Would require Firestore storage. Some way for someone to publish a current config. In the URL, instead of the `default` (for the static JSON) it would be a longer ID...

Be more resilient to simulation runs with very large frame counts

4

Including doing a better job if there is a simulator that never returns a null frame... But be more resilient to that.

Originally captured in #4. Go back to rendering with transparent backgrounds for pngs and make gifs have the default background color composited in the back after the fact (see comment...

Easier-to-compose layouts

1

Instead of bespoke layout logic, allowing layout to use e.g. flexbox and pre-baked components (like diagram-emoji). And then have the lines rendered in an SVG that can... read back those...

Should debug rendering be made a general thing, not part of schelling-org simOptions?

1

Seems like it might be generally useful to pipe in separately

E.g. skin colors, genders, a much larger set

https://tip.golang.org/doc/comment