-
Notifications
You must be signed in to change notification settings - Fork 8
/
Copy pathtodo.txt
43 lines (39 loc) · 1.77 KB
/
todo.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
TODO:
- refactor/clean up
- toolbar
- input handler, setter/getter/comparison/copyload
- cycler
- kaleidoscope/pie slice/snowflake mirroring
- push updates to toolbar
- kill cycling
- smooth transition when adding mouse/touch/keyboard input while cycling
- function that calculates which input set is closest
- add random jitter (spatial + background color)
- drift mode between (preset) cool-looking states
- overlay for orientation
- auto-cycle seed colors
- time reverse
- screenshots/videos -> online image hosting
- "poke me"/safe mode
- change delay for updating
- local transforms -- in mobile, a user fruit-ninja slices across the screen
defining a line segment. The pixels in the vicinity of the line segment are
inverted or mirrored or whatever, and that effect fades out after some
distance.
- More generally, local effects users can control. Local effects are more
intuitive, both for users to control and for incorporating into games, so I
think it would add some entertainment for people too lazy to figure the
feedback loops out. I'm imagining like touching the screen to seed a nice
shimmery dot of light that blends/changes with the surrounding edges.
- fading between scenes
- static image checking --> stop rendering
- anti-strobe: difference checker or exponential averaging
- disable scrolling; disable zooming on mobile
- just for fun:
systematic exploration of phase space, in blocks of camera parameters -- mass save images somewhere
spit out matrix transforms as well, to make it easier to classify
refs:
http://www.vasulka.org/archive/Artists1/Crutchfield,Jim/Space-TimeDynamic.pdf
http://www.gla.ac.uk/schools/physics/staff/johannescourtial/
http://eprints.gla.ac.uk/27/1/414864.pdf
- bool transforms shouldn't change over "state cycling"